By "standard .NET setup project", I assume you mean Visual Studio 2005 setup
and deployment project.
Let's have a look at the Vista installation-related requirements:
Use Windows Components for Installation
Yes, a setup and deployment project creates an MSI.
Support User Account Control for Installation
This basically says the installation shouldn't assume the user installing
will the be same user using the installed components. A setup/deployment
project does nothing in this respect, it's how you implement your particular
setup/deployment. I don't know how this requirement can be evaluated.
Install to Correct Folders
Similarly, setup/deployment defaults to correctly fulfilling this
requirement; but it's up to whomever implements the setup/deployment.
Sign ClickOnce Manifests
Although strictly not part of a setup/deployment project, Visual Studio
2005 supports signing ClickOnce Manifests. You'll have to shell out the
US$999+ to get the certificate to sign your manifest...
Keep ClickOnce Installations Isolated
Again, not a feature of a setup/deployment project directly; it's how you
implement it whether you put user data only in user directories... A
setup/deployment project doesn't stop you from violating this requirement.
Correctly Configure Package Identity
Yes, setup/deployment projects allow you to register the application in
Add/Remove Programs (now Software Explorer).
Install Windows Resources Properly
A setup/deployment project really doesn't do anything on its own. With
this requirement you have to be sure you don't deploy components that aren't
classified as "system" components. a setup/deployment project does nothing
to stop you from doing this.
Follow Best Practices for Creating Custom Actions
Somewhat subjective, and I can't see how this could be validated. See the
requirements for details.
Avoid Reboots During Installation
Also up do the particular implementation of a setup/deployment project.
Support Command Line Installation
Yes
Follow Component Rules
Also detail of the implementation; see requirements to ensure you implement
correctly.
In short, yes, setup/deployment projects allow you to create an installation
the fulfills the Vista installation requirements.
--
Browse
http://connect.microsoft.com/VisualStudio/feedback/ and vote.
http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
"an******@gmail .com" wrote:
I want to deploy a service with a windows app and the setup program
must conform to the Vista certification requirements. Can that be
done with the standard .net setup project? Assuming cost is an
issue,
what else is available?