Running Client Apps on a network drive. Good or bad?
Where I work, we package and deploy are apps to a shared network drive for
easy maintaince. That's what I am told. All of our apps are used in house
and they usually access a SQL Server database on the network. To install
these apps to the clients' computers we go to each machine and run the installation
package installing it back to the shared network drive. We then delete the
uninstall log and proceed to the next machine to do the same installation.
When the users use the application what is going on? Is it being copied
down to their computer or running on the network drive? It makes installation
easy because we can then just recompile and replace the existing exe on the
network. Is this wrong? It works, so I can't argue it. I want to, but
Can someone tell me why I would want to do it any other way.
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL