One .Exe File

[savvaschr]

Hello to All

I have one application in Vb.Net that is used by 11 users that operate
in 11 diferent pcs.
They All have the .exe file on there pc and they connect to an Sql
Server databse that "sits" on a Server. Can I have one .exe on the
server too and all the other pcs oparate on a shorcut of that .exe ?
Cause when i have an upgrade curently i have to go and overwrite
the .exe for all 11 pcs.

Thanks
Savvas

 

[rowe_newsgroups]

Hello to All

I have one application in Vb.Net that is used by 11 users that operate
in 11 diferent pcs.
They All have the .exe file on there pc and they connect to an Sql
Server databse that "sits" on a Server. Can I have one .exe on the
server too and all the other pcs oparate on a shorcut of that .exe ?
Cause when i have an upgrade curently i have to go and overwrite
the .exe for all 11 pcs.

Thanks
Savvas

Yes you can have the application sit on a network share, but it will
be a horror getting all the permissions set up for the user as
application run from a network share have very, very limited rights. A
better solution would be to create a ClickOnce set up project for the
application and deploy it to the network, and have the users link to
this file. Then when it opens it will install itself on the client (or
update itself if it's already installed) with the necessary rights to
run the application. Then when you need to perform updates you just
have to update the ClickOnce file, and the next time a user opens it,
it will be the correct version.

Thanks,

Seth Rowe

 

[\(O\)enone]

Can I have one .exe on the
server too and all the other pcs oparate on a shorcut of that .exe ?

Further to the problems Seth described, another reason why a
centrally-located application .exe that your users run can be a problem is
that while they are running, the .exe file will be locked. When you want to
update it you will need to get everyone to close the application
simultaneously. Sometimes this can be a real pain (especially when you have
situations like a user going on holiday and leaving the app running ...
grr!)

Seth's ClickOnce suggestion sounds like a much better approach.

 

[rowe_newsgroups]

Further to the problems Seth described, another reason why a
centrally-located application .exe that your users run can be a problem is
that while they are running, the .exe file will be locked. When you want to
update it you will need to get everyone to close the application
simultaneously. Sometimes this can be a real pain (especially when you have
situations like a user going on holiday and leaving the app running ...
grr!)

Seth's ClickOnce suggestion sounds like a much better approach.

Actually, my last non-ClickOnce network deployed application I had to
add a kill mode for those types of users. With a change in my config
file it warned the user of impending doom and then shut them down
after so many seconds. This quickly took care of the "holiday" and
weekend users.



Thanks,

Seth Rowe

 

[Patrice]

Or if they have access to a common network share you could update the
application if needed in their login script...

 

[George Shubin]

Use dXLoader to automatically update all 11 workstations when program
changes are need to propagate out to the users. www.dxloader.com

GS