Im attempting to put together a "we must migrate from VB6 to .NET" paper for work. The single biggest stumbling block I have hit upon is how we will manage our application deployment. This is where I am hoping someone here will be able to help.

At present we have a hand crafted deployment system that works a little like Windows Update.
We compile our compile and deploy them, along with an installation script to a central server.
Each machine has a hand crafted update checker tool that monitors for new versions and installs as appropriate.

Basically the Update tool reads the Install Script and uses that to copy, register, delete whatever as needed.
The updater is also intelligent in that the script contains different deployment configurations based on the job a computer does.

Ok, so I need to know if:
a) Do .NET applications require assembly registration in the same way that COMponents do ?
b) I could deploy .NET applications in the same "custom script" way ?, and
c) how easy is it (I cannot find any information on google :s)
 

Any help would be great

Unfortunately Click Once isnt the ticket :/

Ok (its sort of like ADS for applications I believe)...
Our system comprises of:

~35 middleware components (.exe / .dll / .ocx)
~50 client applications (.exe)

~ 15 PCs per site
23 sites.

Our deployment strategy (at the moment) is:

Client machine runs an updater application that monitors a directory for an updated Install.cfg file
The updater application has all of the logic required to parse the Install.cfg, copy and register the components as detailed (and needed) for that machine.

So we deploy the latest components and (if needed) Install.cfg to a directory on the LAN that is monitored by the updater application that is running on each of the client machines.

When the updater detects an update, it prompts the user. Then copies and updates the machine.


So what I need to know is whether it is possible to replicate that behaviour for .NET applications

why dont you just compile to an exe and use AD to deploy the packages.

where? youve got visual studio and i assume an AD?

even if you havent small business server is cheap and brings a plethora of benefits.

Matt