.NET

[#1]

I have just finished converting a VB6 app and need some ideas on how to package it up.

Previously I was using Inno Setup. The executable transfered files and registered the dl for usel.

Is there a packaging and deployment method I should be looking at for .NET applications?

 I have manually added keys to the registry on my computer to autoload the .dll but need to know how to create a setup file to do the same.

Hoping someone can point me in the right direction. 

[#2]

I'm not familiar with Inno Setup, but it will probably still work.

Or you can create a Setup and Deployment project in Visual Studio.

Or you can check these out:

http://through-the-interface.typepad.com/through_the_interface/2011/05/adn-devcast-episode-6-autoloa...

http://through-the-interface.typepad.com/through_the_interface/2011/06/adn-devcast-episode-7-creatin...

On how to use the Autoloader mechanism (if you are on AutoCAD 2012)

[#3]

I used Inno setup without any problems and included the REGDL program from Kean Walmsleys blog to set the registry entries (set to run upon installation in the .iss script):

http://through-the-interface.typepad.com/through_the_interface/2010/02/creating-demand-loading-entri...

[#4]

If your only developing for yourself or friends

Then registry entries are OK, but if you are

Distributing your software then you may not

realise that they only need to load then when

needed.   Using a script file ran from a desktop

shortcut is a good way of doing this.

As for installation, I use MSI Factory, it cost about £300

Pounds, but it's very good.

[#5]

"then you may not realise that they only need to load then when needed.   Using a script file ran from a desktop shortcut is a good way of doing this."

I disagree completely... 

If you are using a script run through a shortcut, then that loads the .dll on AutoCAD startup, every time you use that shortcut to start AutoCAD.  That means you can't start AutoCAD without loading the .dll, then load it into the same session (unless you know how to load it manually, which is not what we're talking about here)

If you set your registry entries correctly, the .dll gets loaded automatically if, and only if, one of it's commands is executed, and if you are using the new autoloader mechanism, it has the same capability (and in fact, it just uses the same registry information as it always has, but it creates the registry entries for you based on the contents of an .xml file)

[#6]

I used to use that very way of starting my .dll but after a series of complaints I changed to a scipt loaded from the desktop shortcut.  Customers didn'y like the fact that if they were in the middle of something and they hit the wrong button other software would start up, and with no dongle plugged in they would have to go & get it, then plug it in.  They may not have the dongle and so forth.

2 cents.

[#7]

JamieRobertson, Would you mind posting an example of your .iss files to do this? 

I have no idea how to code in  Inno Setup and follow code given in Kean's blog.

The 2012 AutoLoader is great but I need to make it supported with earlier versions.

Or does someone have an example of a Setup and Deployment project in Visual Studio?