[2005] Setup Project Installer only install with Specific Operating Systems.

[Icyculyr]

How can I make my project installer only (Setup Project) install if specific operating system conditions are met..

For example, I know my program doesn't work on Windows 98, what happens if someone installs on it? I need it to automatically say 'Invalid operating system' or some error, and list the operating systems supported...

Does anyone know how to do this?

Thanks

[jmcilhinney]

You should look into Launch Conditions. You add them to your Setup project and the installer will refuse to lauch if the specified condition is not met.

[Hack]

Moved to Application Deployment

[isnoend07]

You need an installer that will detect the OS. I spent about 6 hours a few days ago looking at installers. Had to find one that would detect the OS, installers admin rights, path to data folders, detect if a folder exists and optionally create a folder if it does not. Also checked vendors response times to emails. also the setup screens need to be able to add my own graphics. also had to be able to install shortcuts and also check if the files i am installing are newer and then the option to add them or not.
I finally bought this one $70.00
http://www.gdgsoft.com/pb/index.aspx and i gotta say it works good

[dilettante]

Even VSI 1.1 can set Launch Conditions via the Installer Project Properties. I'm sure the VS 2005 Installer Project type allows it as well.

Here's a screenshot from an attempted WinXP install of a Vista-and-later-only MSI package with a simple message I made.

[Icyculyr]

Whats VSI 1.1?

And I would appreciate if you told me how exactly I do that? or perhaps point me in a good tutorial for launch conditions.

Thanks

[jmcilhinney]

Whats VSI 1.1?

And I would appreciate if you told me how exactly I do that? or perhaps point me in a good tutorial for launch conditions.

Thanks

He means VS.NET 2003 (.NET 1.1) Installer projects. If you don't know by now that you can search for launch conditions on MSDN then something is seriously wrong.

[dilettante]

Actually I meant Visual Studio Installer 1.1, for use with VB6. I assumed that later VS Installer Projects are even more liberal feature-wise.

[jmcilhinney]

Actually I meant Visual Studio Installer 1.1, for use with VB6. I assumed that later VS Installer Projects are even more liberal feature-wise.

Ah, incorrect assumption on my part. Launch conditions are a Windows Installer feature and have been supported by VS.NET Setup projects since at least 2003. Probably 2002 as well, if they were supported pre-.NET.

[Icyculyr]

So, do I check what the operating system is via the registry?
(and >>jm, I have looked at the local help on my computer, I didn't understand any of it really)

Can you tell me what registry values to look for?

Cheers

[dilettante]

You'll probably want a Launch Condition expression similar to:

Version9X > 410 Or VersionNT >= 400

This would allow WinMe and NT 4.0 or later. Or maybe:

VersionNT >= 500

This would exclude all Win9X versions and only allow Win2K or later.


I'd expect that the syntax hasn't changed, but I'm not creating .Net deployments so I wouldn't know. I assume there is a toolbar button or menu selection to bring up the Launch Conditions dialog where you enter these expressions. Back in VSI 1.1 they were added on a tab within the Project Properties dialog.