Hi,
Is that an advantage to put the single EXE file that generate by the vb6 on the LAN and let multi-user just point a shortcut to and all running the application from that single EXE copy?
Thanks!
Printable View
Hi,
Is that an advantage to put the single EXE file that generate by the vb6 on the LAN and let multi-user just point a shortcut to and all running the application from that single EXE copy?
Thanks!
Some companies prefer this method, some like to have server scripts "pushing" most recent version to user's workstation on every restart and they also encourage people to actually reboot their machines before they leave... and some companies (mostly very small) don't even bother with either method - local install only.
There is also CITRIX which is a life saver when it comes to deployment...
So it really depends on your business structure.
Reminder: you can only do that if all the dependencies that are required for the app is already installed on all machines. Unless you are running pre configured Virtual Machines.
Oh yes, randem is absolutely right - ALL runtime files must be installed on every user's machine . That's why I love CITRIX - everything is done on the server so as I said deployment is a breeze. :thumb:
Could someone explain to me the advantages or disadvantages of 'pushing' an Exe down from the server to the local machine at each restart ?
Actually I have 'startup' programs that do this now, but I only did it for program updating purposes. For a program that I change that has a lot of users, I can't recompile the Exe on the server while a user is running the application.
So I push it down to their C:\TEMP directory and run the Exe from there.
I'm just curious if I should be doing this for ALL of my programs, or for the ones that aren't used or changed a lot, it won't really matter ?
It's a way to ensure every valid user has most recent version and also all additional files (if any). Also, you leave this in the hands of net admins so it's little less resposibilities for you.Quote:
Originally Posted by tcurrier
Well, the Net admins don't even know my program exists, unless I'm being ignorant.
I'm far from undertstanding operating systems, but I'm curious why I can't recompile a program on the server while a user is 'running' the program? When a user's shortcut points to my program on the server, doesn't the OS actually load the machine code/bytecode, whatever, into their own personal memory ?
Or are the machine instructions actually 'running' on the server ?
If a user shuts down his laptop for the day and goes home, and he didn't 'close' the program, it isn't still actually 'running' on the server, is it ?!?
If the exe is being run the file is actually locked from writting and deleting, so you cannot update it while it is running.
No, nothing is actually running on the server at all.