this comes up on my errors tab when i compile.
it's referring to a setup project which is part of my solution.
Cant find any help on it.
Can someone enlighten me please?
Thanks
Mike
Here's the article on the error message: http://msdn2.microsoft.com/en-us/library/ms228678.aspx
Best regards,
The information is there, it takes a little time to search for though.
Concept: Use the Visual Studio 2005 Bootstrapper to Kick-Start Your Installation http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/default.aspx
Visual Studio tool:
- Publish Page, Project Designer: http://msdn2.microsoft.com/en-us/library/7azx932h.aspx
- Prerequisites Dialog Box: http://msdn2.microsoft.com/en-us/library/7tx0bw8y.aspx
How to:
- Install Prerequisites in Windows Installer Deployment http://msdn2.microsoft.com/en-us/library/7eh4aaa5.aspx
- Install Prerequisites with a ClickOnce Application http://msdn2.microsoft.com/en-us/library/8st7th1x.aspx
Best regards,
So I added a reference to .Net Framework and it was ok.
I agree its not easy to find and they could have been more helpfull and explained how to do it!!
Hope this solves your problem.
Mike
Hi,
Setup projects build Windows Installer packages, so the target machine needs to have Windows Installer 2.0 or greater to run your package.
By default, a bootstrapper is created when you build your Setup project. The bootstrapper is configured to install the .NET Framework 2.0 bootstrapper package, which will install Windows Installer as well.
If you specify that the bootstrapper should be created, but do not specify a bootstrapper package that installs Windows Installer, then this error will appear. Packages that install Windows Installer are '.NET Framework 2.0', 'Windows Installer 3.1', or
'WIndows Installer 2.0' (for downlevel platforms).
To enable/disable the bootstrapper & to pick which packages to install, you can do the following:
1. Right-click on your setup project in the solution explorer
2. Select 'Properties'
3. On the Properties dialog, select 'Prerequisites'
4. In Prerequisites dialog, you will see an option to create the bootstrapper and pick packages to install.
Finally, here's an overview of the bootstrapper: http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/
HTH,
Patrick Darragh
VB PM
Hi, just thought I'd put in my two cents.
Since I used the Setup Wizard project in VB2005, and it seemed to complete without any "problems", yet I have this error message, the suggestion, "Here's the article on the error message" is not really relevant.
The real problem is that the Setup Wizard project does not add all the items necessary to install an application, is it not?
Most of the people who post problems here have already looked into the help file and have come to a dead end, so posting a reference to the unhelpful statements in the help documentation just frustrates people.
Anyway, I'll try Mikepy's straightforward answer and see how that works.
I agree that MSDN and Microsoft in general have some of the worst documentation. In some areas it is very good and detailed with working samples, in other areas it is useless and has NO links or additional information on how to resolve the problem. Unfortunately the good documentation cases are rare. I would think that if Microsoft want to encourage developers to use their tools, they would at the very least provide clear concise documenation.
But as pointed out, the process of using the Setup wizard and "add project output" based on my primary project should be enough for VS 2005 to understand what prerequisites are necessary. But as with everything VS 2005, I keep finding more and more problems with half hearted implementations leaving the developer to go to place like this to try to find answers. This is NOT a productivity enhancer, so far VS 2005 projects have taken considerably longer to develop than VB6 projects, and VS 2003 projects -- is this really Microsoft's "Vision"? If so, time for me to change the channel.
Rob.
After reading all posts and online help, and I think I still have the same problem in mind.
In fact, if I create a new setup project, this warning message " windows installer is not included in any selected prerequisite" is not there at first. If I take the setup file and install it on my computer (same PC as I used to create setup project), and then remove it. Now, if I come back to VS 2005 and open the same setup project, and do a rebuild, I will have this warning message.
Any comments on this?
If I do something as suggested by some posting, I see both Windows Installer 2.1 and 3.0, that seems really interesting.
Is it possible that first time VS 2005 uses a "default" setting and second time we have to provide our choice?
I have the same question. I have 4 projects and they all build fine. This one used to build fine but all of a sudden I am getting that warning:
"Warning 1 Windows Installer is not included in any selected prerequisite"
Why did it all of a sudden come up with that warning?
-Markus_R
I get this warning randomly when building my setup project. My app will always install and run fine whether I get the error or not. For me I just ignore this error and life is fine.
(Thanks to the MS-guys for giving informative answers about the background of this problem, but the next time please also give a useful solution 
.)
No, the solution should be and still is -- Microsoft need to fix VS 2005 Deployment projects -- when one creates a deployment project in VS 2005 based on the primary output of your project file, it should KNOW that .NET 2.0 is a prerequisite and add appropriately. In some cases the build on primary output just doesn't work correctly -- this is what Microsoft need to address to solve the problem at the root.
If you're like me and don't have time to continiously browse MSDN for bugs/problems with VS 2005 then we need real solutions from Microsoft so we don't end up reading a bunch of stuff that is not relevant.
With the resources available to Microsoft, it shameful that I must visit Google/MSDN daily to resolve or R&D problems with VS 2005 -- that just is NOT efficient and just not good for the software industry and clients paying for it. Do you think they wanna pay for my R&D time because Microsoft failed to deliver a solid product? Good luck in getting clients to pay for that.
I don't know what happened to Microsoft, but their level of QA has significantly dropped since about 2001 -- maybe they out source all testing/QA to under qualified 3rd world countries? Whatever they did, it's getting worse not better -- Vista is a clear example of that.
Rob.
