Advice Please

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have vb 6 apps that use sql server for the backend. These apps compile as a standalone exe file. Therefore, I am able to put these in one place on the network and all the users can run the application. I am trying to move these vb 6 apps to vb.net. I can create a folder on the network with the exe and dlls. It works this way, but I would prefer not to have all the dlls in the folder. This causes me to unnecessarily duplicate the dlls on the network. Is the only real option to create an installation package and install each application on the users machines with the dlls? The global assebly cache still seems to require that the dlls are installed on the local machine even though you can create the snk file in a networked locatio

Thanks in advance for any advice
 
Hi John,

Using a very basic install package and setting .net security properly, you
can install the exe and the dlls in a network drive - eg, 'f' - and you
shouldn't have to install the dlls on the local machine. I have apps that
do exactly this and I've had no problem.

HTH,

Bernie Yaeger

John said:
I have vb 6 apps that use sql server for the backend. These apps compile
Click to expand...
as a standalone exe file. Therefore, I am able to put these in one place on
the network and all the users can run the application. I am trying to move
these vb 6 apps to vb.net. I can create a folder on the network with the
exe and dlls. It works this way, but I would prefer not to have all the
dlls in the folder. This causes me to unnecessarily duplicate the dlls on
the network. Is the only real option to create an installation package and
install each application on the users machines with the dlls? The global
assebly cache still seems to require that the dlls are installed on the
local machine even though you can create the snk file in a networked
location
 
Back
Top