Recommendations for deploying a VB.NET multi-client single database application
Posted on 2016-10-10
We have a VB6 app that has been sold to a large number of businesses. The app is installed using a setup program created with Wise for Windows. On the first install at a customer location, it is installed on a workstation/server considered to be the app's "server", and on that install, its MS Access database is created and configured for the business. Subsequent workstation installs include mapping a drive to the location of the database, and "connecting" the app to the database via the mapped drive. Updates are created as patches placed on our cloud server. The local app checks the server for updates when it starts, then downloads and applies the patch if one is found for a higher version than the app.
We are rewriting the app in VB.NET and looking for the best approach for installing and upgrading the app. We've looked at ClickOnce, but feel that it's not flexible enough for what we're trying to accomplish.
1, Is anyone managing a similar app using ClickOnce?
2. Does anyone have a suggestion for a different approach?