Topic: Auto deployment of .net executables?

[Bob Q]

Hi we have created several .net programs that simply display a dialog box on the desktop.
We have had to install the program on each computer in the company, and updates are becoming a PIA.
So I was wondering if there is any way to reference an executable off a server location versus putting it on each computer, so that when we make changes, the new changes automatically show up on the computers?

I attached a screen shot of what the program does. It is simply a means to provide permanent shortcuts to different directories on our company server., and one area runs a search utility.
The program is set up so that you can not close it out or move it around. This way no one looses track of the short cuts etc.

We put the .exe in the startup folder so it runs everytime the computer is rebooted.

Thanks!

[MP]

Why not just have a batch file / script / etc. in the start-up folder that runs executable(s) that reside on the network?

[BillZndl]

I just use a shortcut on the desktops that reference the exe from a network location.

[Bob Q]

Hmmmmm I thought we tried that..... can't remember.
It sure makes sense though.
And it doesn't make any sense that it wouldn't work!
So maybe we didn't try it. Got me!
I will give it a go, thanks!
I will report back.

[dgorsman]

Why not just have a batch file / script / etc. in the start-up folder that runs executable(s) that reside on the network?

We do this.  Plus for in-house designs I try to keep data out of the program where possible, placing it in the registry, a local data file, or a network data file, whichever is most useful.  Data files and registry settings are far easier to keep up-to-date than executeables.

[MP]

Be careful with shortcuts as they're sometimes too smart -- if you move the target a shortcut points to it (sometimes) reflects the move. So when updating a network executable that is the target of desktop shortcuts overwrite it directly. If you need to make a backup for historical purposes copy it, but don't move it and replace it with a new executable, that can cause a heap of headaches requiring updating all the shortcuts, which kinda thwarts the whole "less work every time the executable needs to be updated".

[MP]

... for in-house designs I try to keep data out of the program where possible, placing it in the registry, a local data file, or a network data file, whichever is most useful.  Data files and registry settings are far easier to keep up-to-date than executeables.

√ Always a good strategy, even for simple LISP proggies.

[Jeff H]

I use one .net plug-in that has looks for a certain file which contains just xml and it is basically copy and load instructions. Copy subfolders, file filter, etc......

Then create a build configuration that is set to path on network so next time they startup autocad it checks if files or newer, if it needs to delete missing files then loads them.

Makes it easy to update any ribbons, .net apps, etc......

[n.yuan]

Hello, everyone forgot "ClickOnce"? It simple with auto-update mechanics built in. It is perfect for desktop app deployment.

[BillZndl]

Be careful with shortcuts as they're sometimes too smart --

Our few "public apps" are in one network folder with security settings so we don't move them around.
Biggest pain is when updating an app, you have to make sure no one is using it before you can replace the file.
Don't know of a way around that.