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.