Installing with Shortcut to exe on network

[demotivater]

I'm trying to create an install package with all necessary files, except instead of an exe installed locally, I just want to install shortcuts to an exe on the network so I can update only one exe when I need to. I can't figure this out at all, has anyone done this before, any tips?

Thanks

[szlamany]

We do this...

It's been a while since we created the SETUP package, but I believe we simply edited the setup files to not install the .EXE, but left the install commands for the few DLL and OCX files.

I think the customer keeps the shortcut to the .EXE up on a groups share - they actually push out several copies of the .EXE to "more local" building servers whenever we make a change.

For some reason they frown upon desktop shortcuts...

[szlamany]

Quick point...

Since we run with .EXE on network, we also control (from within our SQL database) what version of the .EXE is allowed to run. This is in case the user has copied an old version of the .EXE to a local drive, we can disallow it from running.

We also track (in the SQL database) each .EXE connection, with where the APP.PATH was and what the APP version info is (along with user machine time, username, yadda, yadda)...

[demotivater]

I'm going to try this afternoon to make this work. Good points in the second post. Thanks