K
KenKrugh
Guest
New to VS and .net (yeah, I know, just a tad late to the game) and we're upgrading some small, mostly uncomplicated VB6 apps that are run from a network drive on both workstations and users on an application server.
With the VB6 apps we'd run an install if necessary to put whatever components were needed on the workstation (dlls or OCXs) then all workstations and app server users had a tool bar on the task bar that pointed to the network drive. If an app needed tweaking we'd just update the exe that everyone's task bar was pointing to and everyone was good to go.
After a couple of hours of research it appears there a zillion extensions I can use in VS that all seem to pretty much do the same thing.
I'm also considering simply pointing the shortcuts on everyone's machine to the exe in the "bin" folder, similar to what we were doing with the VB6 apps. For that I'd need to run a setup on the work stations to get the dlls copied and registered. Is there a "best practice" or preferred method for creating "non-ClickOnce" apps?
Would love to hear some ideas/opinions.
Many thanks!
Ken
Continue reading...
With the VB6 apps we'd run an install if necessary to put whatever components were needed on the workstation (dlls or OCXs) then all workstations and app server users had a tool bar on the task bar that pointed to the network drive. If an app needed tweaking we'd just update the exe that everyone's task bar was pointing to and everyone was good to go.
After a couple of hours of research it appears there a zillion extensions I can use in VS that all seem to pretty much do the same thing.
I'm also considering simply pointing the shortcuts on everyone's machine to the exe in the "bin" folder, similar to what we were doing with the VB6 apps. For that I'd need to run a setup on the work stations to get the dlls copied and registered. Is there a "best practice" or preferred method for creating "non-ClickOnce" apps?
Would love to hear some ideas/opinions.
Many thanks!
Ken
Continue reading...