I'm using Visual Studio 2005. Is it possible to set up a prerequisite
(for Windows Installer 2.0) so that it doesn't download and/or try to
install the item, but rather simply outputs a message stating that it
needs to be done?
Thanks,
Dave
You must be using the bootstrapper, right? MSI files have a built-in check
(in the summary information of the MSI file, the schema level) that in the
case of VS 2005 setups is already set to require MSI 2.0. If it's not on the
system Windows will tell you it can't launch the MSI file. So the built-in
Windows prerequisite is already there, and you just need to turn off the one
you're seeing, which might be from the bootstrapper prerequisite settings in
your setup project, the exe.

Signature
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280
> I'm using Visual Studio 2005. Is it possible to set up a prerequisite
> (for Windows Installer 2.0) so that it doesn't download and/or try to
[quoted text clipped - 3 lines]
> Thanks,
> Dave
headware - 21 Jun 2006 17:29 GMT
Phil,
Thanks for the help. You're right, I am using the bootstrapper.
I didn't realize the Windows Installer 2.0 requirement was a setting in
the MSI file. Ideally, I would like to support Windows ME without
requiring the user to download anything. Is there a reason the MSI file
is set to require Windows Installer 2.0 or above? I ask because that
precludes it from working with Windows ME as it comes out of the box.
Is there a way (and is it a good idea) to lower the version requirement
to 1.2 or does it have to be 2.0?
Thanks,
Dave
> You must be using the bootstrapper, right? MSI files have a built-in check
> (in the summary information of the MSI file, the schema level) that in the
[quoted text clipped - 16 lines]
> > Thanks,
> > Dave
Phil Wilson - 22 Jun 2006 15:13 GMT
MSI 2.0 provides support for installing .NET things like assemblies.

Signature
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280
> Phil,
>
[quoted text clipped - 37 lines]
>> > Thanks,
>> > Dave
headware - 22 Jun 2006 16:57 GMT
Well the app isn't dependent on the .NET framework. It's all done in
Win32 API. So is there a way to change that MSI version requirement in
the file?
Thanks,
Dave
> MSI 2.0 provides support for installing .NET things like assemblies.
> --
[quoted text clipped - 44 lines]
> >> > Thanks,
> >> > Dave
Phil Wilson - 22 Jun 2006 18:24 GMT
Well that was just one of the changes. I assume Visual Studio sets the
schema to 2.0 because it needs something in MSI 2.0 from this list:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/what_
s_new_in_windows_installer_version_2_0.asp?frame=true
If you want to experiment, get Orca from the Platform SDK (install from
Orca.msi), open the MSI file. View->Summary Information, change the schema
to 120.

Signature
Phil Wilson [MVP Windows Installer]
----
> Well the app isn't dependent on the .NET framework. It's all done in
> Win32 API. So is there a way to change that MSI version requirement in
[quoted text clipped - 57 lines]
>> >> > Thanks,
>> >> > Dave