"Mark White" <ma*******@yahoo.com> wrote in message
news:eb**************@TK2MSFTNGP12.phx.gbl...
I'm curious, is there a specific reason why you don't use a Setup and
Deployment project?
Mark
For me, I like how Inno Setup is. It allows you to create setup packages
regardless of the development language used. It contains 1 file (the setup
file) unless you write include scripts to go along with it. I can attach
this single file to a .Net project (or any other source-controlled project
in any language) in order to keep it under source control. The syntax isn't
hard to understand and ISTool (a GUI front-end to InnoSetup) makes the task
of creating a setup for an application, library, et cetera pretty darn easy.
The .Net Setup and Deployment project is more complex and yet, limited. For
example, how hard is it to get the output of the Setup and Deployment
project to contain the following:
<Static Name Of Setup> v<major>.<minor>.<exe or msi>
There may be a way, but I have asked before and never found out how. Now,
the decision was not based on that example, but quite a few similar
annoyances with .Net's Setup and Deployment projects and the features of
Inno Setup just made Inno Setup a better choice for our organization.
:)
Mythran