Can someone suggest the proper/best method for deploying a VB.NET/SQL Server 2000 to 50+ users? I have an application that needs to be accessible to 50+ users, and don't know the best method for deployment. My users are in several different physical locations, all on a VPN and all are internal users. Some questions:
1. Do I package my application and deliver it to all of my users, having them run the .msi or setup file? Obviously, that would result in a fat client, and anytime an upgrade has to be delivered, it has to be deployed to every user.
2. Do I just install the application to a server and have everyone run it from there? That helps with the upgrades and maintenance issues, but was wondering how that would impact performance.
This application is one that's already in development that I'm inheriting soon. If someone has some suggested reading or suggestions they can post here, I'd really appreciate it!
Thanks.
Steve
1. Do I package my application and deliver it to all of my users, having them run the .msi or setup file? Obviously, that would result in a fat client, and anytime an upgrade has to be delivered, it has to be deployed to every user.
2. Do I just install the application to a server and have everyone run it from there? That helps with the upgrades and maintenance issues, but was wondering how that would impact performance.
This application is one that's already in development that I'm inheriting soon. If someone has some suggested reading or suggestions they can post here, I'd really appreciate it!
Thanks.
Steve