oafc0000 Posted February 5, 2003 Posted February 5, 2003 Hey Guys and Girls 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. Can anybody help? Thanks in advance Quote
Cywizz Posted February 5, 2003 Posted February 5, 2003 What type of errors are you getting? Does all the PC's that need to run this, have the Framework installed? PS. I'm glad someone found it easy to work with the 'DLL hell' of vb6 :) Quote Howzit??
oafc0000 Posted February 5, 2003 Author Posted February 5, 2003 Hi Mate VB6 was far from easy when it came to DLLS :P The framework is installed but I have created a package to install it localy, basically to place the required Dlls on the users PC. The error is saying --------------------------------------------------------------------------- Application has generated an exception that could not be handled. Process id=0xd9 (217), Thred id=0x101 (257) --------------------------------------------------------------------------- When it ran off the network drive. It runs fine locally Quote
Cywizz Posted February 5, 2003 Posted February 5, 2003 Is the dependancies, the dll's on the client's machines, also on the network machine, with the exe? Quote Howzit??
oafc0000 Posted February 5, 2003 Author Posted February 5, 2003 NO :) That would be it wouldnt it I'll give it ago and come back to you Thanks Quote
Cywizz Posted February 5, 2003 Posted February 5, 2003 To give you a suggestion: 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 :) Cheers Quote Howzit??
*Gurus* divil Posted February 5, 2003 *Gurus* Posted February 5, 2003 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. Quote MVP, Visual Developer - .NET Now you see why evil will always triumph - because good is dumb. My free .NET Windows Forms Controls and Articles
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.