deploying VB6 applications in a production environment 1

[jasperjasper]

I would like to hear from you guys out there...as for deploying your VB6 apps, say you have 25 users...and you make a minor change to the app, do you have to rebuild(compile) and create a package then install on each workstation for each change no matter how trivial.

Please shed some light on this. Thanks

 

[bboffin]

The short answer is yes because that's the correct and safe way to do it.

If however the change was a simple bug fix and no external packages or components were changed you will probably get away with redistributing the .exe file.

Try it on one production machine first to make sure and don't forget to change the version number. Also make sure that the version number can be displayed in the program, usually in an About form otherwise it can be difficult to check which version is being used.


Bob Boffin

 

[jasperjasper]

Thanks for your response. But if you have 50 users you would still need to copy the new EXE onto their pcs right?
This is a pain in the ass. I have been doing Access apps for the past two years, and now I am wondering why anyone would want to use VB?

You know when you put something into production, and there are some small simple issues that users want that are easy... how do you handle this with VB. You keep having to install the exe onto their pc...

 

[bjd4jc]

Do all 50 of your users reside on the same network? If so you can store the exe file on the network and create a shortcut on 50 user's PC that points to the network location. Then, when you have a bug fix then you update the network copy (while no one is using it) and then every has the update next time they run it. In a corporate environment I wouldn't run an executable locally on computers. I gather from your comments about Access that your users are using the same network. I've created a "common" VB6 setup package that would contain almost all components that I would use and then that is installed on each computer. Then I just point users to executables on the network. Always worked out fine. The only time you would have to repackage and reinstall is if you used a component that was not included in the original "common" package.

 

[jasperjasper]

Yes, all the users reside on the same network. So, for instance, if several VB apps have already been deployed that "common" package of controls already exists (most likely) so if I create a new VB6 app, I could place the exe on the network, create a shortcut to it on their workstations, and that approach could work.
Then with that first deployment, there could be cosmetics and simple changes, so I could create a new exe, point it to the network location, and that could work...

OK...its very similar to Access deploymet in that way.

 

[ZmrAbdulla]

Hi,
Sorry to interrupt....
I am creating an EXE to use it in our network that includes about 200 pcs. I like the suggestion given by bjd4jc to keep the file in server and create shortcuts on the pcs. My question is how many users can open the EXE at a time?

My application includes some help & information files in HTML format. At present I am using HTML help workshop to create an EXE. This is kept in a network folder. All the users are able to open at the same time. Now I wish to give the application a new interface. So wished to migrate to VB.
Do you think VB can handle this situation?

Thanks for any input


Zameer Abdulla

http://www.geocities.com/zameerabd/

 

[UKmedia]

ZmrAbdulla:

The exe can handle many instances so one million users would be ableto use it. Only issue here is that is that your sever must never go down otherwise the app won't work.

When you have a network app you need to bear in mind all of your references to files (i.e. help file etc....)

When you want to upgrade you app I find it best if database app then have a field in there that you update and have a timer on your app looking at this field every so ofter (5mins) to kick eveyone out of the exe so you can upgrade. This way if someone trys to open the app then it will warn them that an upgrade is going though please wait.

I use a standard exe that will link to my main exe so that way if users do try and open the app it will prevent them from opening my main exe that I am upgrading.

Hope this helps

UKmedia productions

http://www.uk-media.com

 

[ZmrAbdulla]

Hi,
Thanks for that tips.
One million users?! It is incredible!
Normally our server keeps running without any trouble.
Upgrade of the EXE is merely required. It is only a form with WebBrowser control. It is something like an Intranet.Users can browse Intranet, Websites of the Group (it is a group of companies),Help pages, Informations etc.. All are controlled from the menu. I am keep on updating the HTML pages that won't be a problem even if the user is inside EXE.
I didn't understand the system that you described to upgrade
TextBox and bla.. No problem.. I will learn it later..
Thanks again

Zameer Abdulla

http://www.geocities.com/zameerabd/