Visual Studio and Networking

[jacobpressures]

I heard that I could configure VSI for network setup. I was told that this means that the application I create can be placed on a server to share over our office's network and users can run the application from there and access it from their computers.

1) Is this difficult to do? Are there any problems or issues i need to work out if i decide to do it this way? We were going to install the app on each individual computer. But i would rather put it on the server so that I don't have to do multiple updates if the program needs to be changed.

2) How do i find good instructions on how to get this done if i choose to do it this way?

Thanks. these are very important questions for me. I'm almost ready to deploy my app and i'm a little scared.

 

[ArtieChoke]

It's not difficult at all, but there are some things you'll have to do:

- Give users access to the network share/directory where the exe file will be stored

- If your program uses dll files, then you will need to place them on the share also. In addition, you will need a way to register them on the user's machines. They can reside on the server, but must be registered. I created a registration class that will allow the program to detect if the dll files aren't registered and register them on the machine. Let me know if you would like to use it. There is another way to do it in VB, but you have to hard-code the file names. That's why I made a generic class to do it, and pass the names via a file. You can also create a batch file that uses regsvr32 if you'd rather do it manually.

- Create shortcuts to the program and give those to the users instead of directly accessing the exe file - this will allow you to set up the working directory in case there are support files that are needed, but don't get registered, like for Crystal Reports, for instance.

"I think we're all Bozos on this bus!" - Firesign Theatre

 

[jacobpressures]

Is it better to just install it on all the machines using the network?

If i tried the server thing, that you described above, will it be easy to test and troubleshoot?

If i decide to to do it the way you described, you will need your program because i have the slightest idea how to make one and don't have the time.

Thanks very much!!!!

 

[ArtieChoke]

All you have to do to test is put the exe on the network and run it from there on your machine and one that doesn't have VB installed to verify it works.

If you have a lot of users, it's much better to put it on the network. Otherwise, the next upgrade means you touch all their machines or have them run an install - argh!

If you don't have much time, I suggest using a batch file with regsvr32. If you use the /s option, it will install quietly (no user interaction). You will need to have each user run it once before trying to run the program. Use an UNC name for the files, ie. \\myserver\mydir\mydll, etc. so it's always reachable. You will need a share set up to access the network directory. If you have DFS, then that would make it a bit easier.

You can always do the install on each machine and then try this method out when you have the time.



"I think we're all Bozos on this bus!" - Firesign Theatre

 

[jacobpressures]

Thanks! I have a little time to prepare. It will be within the next week or so.

How can i find out more information. What do i look up or do you know of any articles that will help. That way i can go step by step or something and learn what my options are.

 

[jacobpressures]

I was told that on a so-called "busy" network having the app installed on the server could cause problems. I don't think our network is that busy however, the only thing it is used for in internet access.

 

[ArtieChoke]

See this article by MS for registering within the program (note: this is the one that has hard-coded dll file names):

http://support.microsoft.com/default.aspx?scid=kb;en-us;173407

Also, see this writeup on regsvr32:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/regsvr32.mspx

I'm not clear on what problems a "busy" network would cause - most likely just long loading times.

"I think we're all Bozos on this bus!" - Firesign Theatre

 

[jacobpressures]

Thanks man! very much appreciated. I'm going to read the articles