In VB6 all you had to do to run a application over a network was to place the exe on one of the drives and then place all required dlls on the PCs that want to run it.
Tried doing the same in VB.net but with no joy. I keep getting weird errors.
Create an install that only installs a stub (small exe) on all your clients. The stub can then dynamicly load the depenancies from the network, using the Reflection namespace (You can look up details on the 'Assembly.LoadFrom' method.)
This way, you only need to update the network dll's if you need to update the client's with new versions.
Currently I use a webservice internally to update our client app's, and let me tell you.... it is much better than creating installs
By default .NET security prevents assemblies from being run from a network share. You can change this via the .NET settings pages in Administrative Options under the Control Panel.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.