|
|
You're in the
dotnet setup
group:Order of Launch Conditions
dotnet setup:
morning. Thanks again, Brian. [quoted text, click to view] "Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message news:uSsdXPAeFHA.2076@TK2MSFTNGP15.phx.gbl... > 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@127.0.0.1.activesol.co.uk> wrote in message > news:1119524770.10427.0@doris.uk.clara.net... >>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. >> >> >> > >
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 [quoted text, click to view] "Brian Cryer" <brianc@127.0.0.1.activesol.co.uk> wrote in message news:1119524770.10427.0@doris.uk.clara.net... >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. > > >
See the thread "help: iis not running asp.net" starting 6/22/2005 in
microsoft.public.vsnet.setup - same general story. -- Phil Wilson [MVP Windows Installer] ---- [quoted text, click to view] "Brian Cryer" <brianc@127.0.0.1.activesol.co.uk> wrote in message news:1119544442.13147.0@eunomia.uk.clara.net... > Thanks Phil. Knowing I can't is useful. I'll give aspnet_regiis a go in > the morning. > > Thanks again, > > Brian. > > > "Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message > news:uSsdXPAeFHA.2076@TK2MSFTNGP15.phx.gbl... >> 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@127.0.0.1.activesol.co.uk> wrote in message >> news:1119524770.10427.0@doris.uk.clara.net... >>>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. >>> >>> >>> >> >> > >
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.
Thanks, and you were quite right. aspnet_regiis -ir resolves the problem. :)
Brian. [quoted text, click to view] "Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message news:%23y%23uaACeFHA.3932@TK2MSFTNGP12.phx.gbl... > See the thread "help: iis not running asp.net" starting 6/22/2005 in > microsoft.public.vsnet.setup - same general story. > -- > Phil Wilson [MVP Windows Installer] > ---- > "Brian Cryer" <brianc@127.0.0.1.activesol.co.uk> wrote in message > news:1119544442.13147.0@eunomia.uk.clara.net... >> Thanks Phil. Knowing I can't is useful. I'll give aspnet_regiis a go in >> the morning. >> >> Thanks again, >> >> Brian. >> >> >> "Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message >> news:uSsdXPAeFHA.2076@TK2MSFTNGP15.phx.gbl... >>> 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@127.0.0.1.activesol.co.uk> wrote in message >>> news:1119524770.10427.0@doris.uk.clara.net... >>>>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. >>>> >>>> >>>> >>> >>> >> >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |