Re: Order of Launch Conditions
- From: "Phil Wilson" <pdjwilson@xxxxxxxxxxxxxx>
- Date: Thu, 23 Jun 2005 08:01:47 -0700
No you can't - they're not sequenced in any forced order in the MSI file,
it's just a list. When you installed IIS first, the .NET framework install
integrated with it, that's why it worked. But you could have fixed that by
(probably) running aspnet_regiis if you'd installed .NET then IIS.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280
"Brian Cryer" <brianc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1119524770.10427.0@xxxxxxxxxxxxxxxxxxxxx
>I have a relatively simply (demonstration) vb.net program which runs in a
>browser. Because of factors outside of my control, I will need to install
>and run this locally on pcs rather than from a single webserver. Having put
>together a deployment package for this (which works fine on my pc) I have a
>problem when installing on a fresh windows 2000 workstation. The problem
>appears to be related to the order in which the deployment project
>considers the launch conditions:
>
> .NET Framework
> IIS Condition - i.e. is IIS installed
>
> I think this order is wrong. I think it should check that IIS is installed
> and then .NET - or at least the prompt saying you need IIS should come
> first. This is because my installation worked if I (manually) installed
> IIS and then .NET but not when I did it the other way round.
>
> So my question is, how can I change the order in which the installer
> considers the launch conditions?
>
> Thanks,
>
> Brian.
>
>
>
.
- Follow-Ups:
- Re: Order of Launch Conditions
- From: Brian Cryer
- Re: Order of Launch Conditions
- References:
- Order of Launch Conditions
- From: Brian Cryer
- Order of Launch Conditions
- Prev by Date: Order of Launch Conditions
- Next by Date: Re: Order of Launch Conditions
- Previous by thread: Order of Launch Conditions
- Next by thread: Re: Order of Launch Conditions
- Index(es):
Relevant Pages
|