|
|
You're in the
dotnet setup
group:.NET Framework Bootstrapper in a Setup
dotnet setup:
I plan to use the following installation scenario, involving the sample .NET Framework Bootstrapper. 1. Ask the user to dowload the dotnetfx.exe from the Win Update site; 2. Search for the dotnetfx.exe file on the client machine and if found, get the path to it; 3. Change Settings.ini (FxInstallerPath line) to point to this path; 4. Start or instruct the user to click Setup.exe (the .NET Framework Bootstrapper) - this would start the actual installation by checking for the Framework and installing it, if not there, then doing the same for Windows Installer and, eventually, installing my application. The question is whether this can be acieved by a Setup project or I need to write a custom Installer class? TIA
A setup project has built in support for this. See:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/vxgrfInstallUrlProperty.asp (I wouldn't *search* for a dotnetfx.exe on the client system anyway - this is the generic name for all the redistributable exe files for all the versions, so you could find the wrong one.) You can't write a custom installer class anyway - you can only run on MSI-based install at a time, and while yours is running the MSI-BASED dotnetfx won't run properly. This is also an option: http://www.codeproject.com/dotnet/dotNetInstaller.asp -- Phil Wilson [MVP Windows Installer] Definitive Guide to Windows Installer http://www.amazon.com/exec/obidos/tg/detail/-/1590592972/104-7044380-4696760 [quoted text, click to view] "sprungli" <sprungli1@netscape.net> wrote in message news:%23l$wkDypEHA.3396@tk2msftngp13.phx.gbl... > Hello, > > I plan to use the following installation scenario, involving the sample > .NET > Framework Bootstrapper. > > 1. Ask the user to dowload the dotnetfx.exe from the Win Update site; > 2. Search for the dotnetfx.exe file on the client machine and if found, > get > the path to it; > 3. Change Settings.ini (FxInstallerPath line) to point to this path; > 4. Start or instruct the user to click Setup.exe (the .NET Framework > Bootstrapper) - this would start the actual installation by checking for > the > Framework and installing it, if not there, then doing the same for Windows > Installer and, eventually, installing my application. > > The question is whether this can be acieved by a Setup project or I need > to > write a custom Installer class? > > TIA > >
Ok, I was looking at VS 2003 setup projects. VS.NET is slightly different,
so all you have is the launch condition. I think that MsiNetAssemblySupport *is* a launch condition that checks for the 1.0 framework. The bootstrapper installs the Windows Installer engine, but the Windows Installer engine is installed when you install the framework. If the framework has been installled, you don't need a bootstrap, just the MSI file. -- Phil Wilson [MVP Windows Installer] [quoted text, click to view] "sprungli" <sprungli1@netscape.net> wrote in message news:OwhBPx7pEHA.3988@tk2msftngp13.phx.gbl... > Thank you Phil, > > The 1st option fits to my deployment needs. However, a .NET Framework > Launch > Condition is not included by default in the Launch Condition editor of my > setup project(although there is a detected dependency) and when I try to > add > it manually, the new condition doesn't contain properties like InstallUrl > or > SupportedRuntimes. Apart from the name it only has two props: Condition > (MsiNetAssemblySupport) and Message ([VSDNETMSG]). I guess this is not the > NET Framework Launch Condition. Also what should be the value of the > Bootstrapper in this scenario? (My guess is Win Installer Bootstrapper.) > > Note: I am w/ VS.NET and the 1.0 Framework. > > > > "Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message > news:enYPoL2pEHA.708@tk2msftngp13.phx.gbl... >> A setup project has built in support for this. See: >> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/vxgrfInstallUrlProperty.asp >> >> (I wouldn't *search* for a dotnetfx.exe on the client system anyway - >> this >> is the generic name for all the redistributable exe files for all the >> versions, so you could find the wrong one.) >> You can't write a custom installer class anyway - you can only run on >> MSI-based install at a time, and while yours is running the MSI-BASED >> dotnetfx won't run properly. This is also an option: >> http://www.codeproject.com/dotnet/dotNetInstaller.asp >> -- >> Phil Wilson >> [MVP Windows Installer] >> Definitive Guide to Windows Installer >> > http://www.amazon.com/exec/obidos/tg/detail/-/1590592972/104-7044380-4696760 >> >> "sprungli" <sprungli1@netscape.net> wrote in message >> news:%23l$wkDypEHA.3396@tk2msftngp13.phx.gbl... >> > Hello, >> > >> > I plan to use the following installation scenario, involving the sample >> > .NET >> > Framework Bootstrapper. >> > >> > 1. Ask the user to dowload the dotnetfx.exe from the Win Update site; >> > 2. Search for the dotnetfx.exe file on the client machine and if found, >> > get >> > the path to it; >> > 3. Change Settings.ini (FxInstallerPath line) to point to this path; >> > 4. Start or instruct the user to click Setup.exe (the .NET Framework >> > Bootstrapper) - this would start the actual installation by checking >> > for >> > the >> > Framework and installing it, if not there, then doing the same for > Windows >> > Installer and, eventually, installing my application. >> > >> > The question is whether this can be acieved by a Setup project or I >> > need >> > to >> > write a custom Installer class? >> > >> > TIA >> > >> > >> >> > >
Thank you Phil,
The 1st option fits to my deployment needs. However, a .NET Framework Launch Condition is not included by default in the Launch Condition editor of my setup project(although there is a detected dependency) and when I try to add it manually, the new condition doesn't contain properties like InstallUrl or SupportedRuntimes. Apart from the name it only has two props: Condition (MsiNetAssemblySupport) and Message ([VSDNETMSG]). I guess this is not the NET Framework Launch Condition. Also what should be the value of the Bootstrapper in this scenario? (My guess is Win Installer Bootstrapper.) Note: I am w/ VS.NET and the 1.0 Framework. [quoted text, click to view] "Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message news:enYPoL2pEHA.708@tk2msftngp13.phx.gbl... > A setup project has built in support for this. See: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/vxgrfInstallUrlProperty.asp > > (I wouldn't *search* for a dotnetfx.exe on the client system anyway - this > is the generic name for all the redistributable exe files for all the > versions, so you could find the wrong one.) > You can't write a custom installer class anyway - you can only run on > MSI-based install at a time, and while yours is running the MSI-BASED > dotnetfx won't run properly. This is also an option: > http://www.codeproject.com/dotnet/dotNetInstaller.asp > -- > Phil Wilson > [MVP Windows Installer] > Definitive Guide to Windows Installer > http://www.amazon.com/exec/obidos/tg/detail/-/1590592972/104-7044380-4696760 > > "sprungli" <sprungli1@netscape.net> wrote in message > news:%23l$wkDypEHA.3396@tk2msftngp13.phx.gbl... > > Hello, > > > > I plan to use the following installation scenario, involving the sample > > .NET > > Framework Bootstrapper. > > > > 1. Ask the user to dowload the dotnetfx.exe from the Win Update site; > > 2. Search for the dotnetfx.exe file on the client machine and if found, > > get > > the path to it; > > 3. Change Settings.ini (FxInstallerPath line) to point to this path; > > 4. Start or instruct the user to click Setup.exe (the .NET Framework > > Bootstrapper) - this would start the actual installation by checking for > > the > > Framework and installing it, if not there, then doing the same for Windows > > Installer and, eventually, installing my application. > > > > The question is whether this can be acieved by a Setup project or I need > > to > > write a custom Installer class? > > > > TIA > > > > > >
Thanks again,
so this would mean I should revert to the scenario of my 1st post, since there is just a check for the existance of the Framework, not an installation option. Do you, by any chance, know if the .NET Framework Bootstrapper accepts an URL path to the dotnetfx.exe? In this case I could just set FxInstallerPath to the URL address where the dotnetfx.exe for the1.0 version can be downloaded. It is difficult for me to test at this time, that is why I am asking. Regards, s. [quoted text, click to view] "Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message news:e5TiKe8pEHA.3592@TK2MSFTNGP14.phx.gbl... > Ok, I was looking at VS 2003 setup projects. VS.NET is slightly different, > so all you have is the launch condition. I think that MsiNetAssemblySupport > *is* a launch condition that checks for the 1.0 framework. The bootstrapper > installs the Windows Installer engine, but the Windows Installer engine is > installed when you install the framework. If the framework has been > installled, you don't need a bootstrap, just the MSI file. > -- > Phil Wilson > [MVP Windows Installer] > "sprungli" <sprungli1@netscape.net> wrote in message > news:OwhBPx7pEHA.3988@tk2msftngp13.phx.gbl... > > Thank you Phil, > > > > The 1st option fits to my deployment needs. However, a .NET Framework > > Launch > > Condition is not included by default in the Launch Condition editor of my > > setup project(although there is a detected dependency) and when I try to > > add > > it manually, the new condition doesn't contain properties like InstallUrl > > or > > SupportedRuntimes. Apart from the name it only has two props: Condition > > (MsiNetAssemblySupport) and Message ([VSDNETMSG]). I guess this is not the > > NET Framework Launch Condition. Also what should be the value of the > > Bootstrapper in this scenario? (My guess is Win Installer Bootstrapper.) > > > > Note: I am w/ VS.NET and the 1.0 Framework. > > > > > > > > "Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message > > news:enYPoL2pEHA.708@tk2msftngp13.phx.gbl... > >> A setup project has built in support for this. See: > >> > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/vxgrfInstallUrlProperty.asp > >> > >> (I wouldn't *search* for a dotnetfx.exe on the client system anyway - > >> this > >> is the generic name for all the redistributable exe files for all the > >> versions, so you could find the wrong one.) > >> You can't write a custom installer class anyway - you can only run on > >> MSI-based install at a time, and while yours is running the MSI-BASED > >> dotnetfx won't run properly. This is also an option: > >> http://www.codeproject.com/dotnet/dotNetInstaller.asp > >> -- > >> Phil Wilson > >> [MVP Windows Installer] > >> Definitive Guide to Windows Installer > >> > > http://www.amazon.com/exec/obidos/tg/detail/-/1590592972/104-7044380-4696760 > >> > >> "sprungli" <sprungli1@netscape.net> wrote in message > >> news:%23l$wkDypEHA.3396@tk2msftngp13.phx.gbl... > >> > Hello, > >> > > >> > I plan to use the following installation scenario, involving the sample > >> > .NET > >> > Framework Bootstrapper. > >> > > >> > 1. Ask the user to dowload the dotnetfx.exe from the Win Update site; > >> > 2. Search for the dotnetfx.exe file on the client machine and if found, > >> > get > >> > the path to it; > >> > 3. Change Settings.ini (FxInstallerPath line) to point to this path; > >> > 4. Start or instruct the user to click Setup.exe (the .NET Framework > >> > Bootstrapper) - this would start the actual installation by checking > >> > for > >> > the > >> > Framework and installing it, if not there, then doing the same for > > Windows > >> > Installer and, eventually, installing my application. > >> > > >> > The question is whether this can be acieved by a Setup project or I > >> > need > >> > to > >> > write a custom Installer class? > >> > > >> > TIA > >> > > >> > > >> > >> > > > > > >
I don't believe FxInstallerPath will take a URL, although I haven't tried
it. The detection on VS.NET isn't as flexible as VS 2003. VS.NET uses the standard Windows Installer property MsiNetAssemblySupport to look for the framework, and that property is set to the latest version and includes 1.1 and later - it's set if there is ANY framework on the system. I think this means that VS.NET has no built-in way to let you check explicitly for the 1.0 framework. In fact, your setup will not even launch unless there is a version of the framework on the target system. VS 2003 is more flexible because it has a SupportedRuntimes property to tell VS which versions to check for, and an InstallUR property to download it from. In your situation I'd use the http://www.codeproject.com/dotnet/dotNetInstaller.asp type of solution, or upgrade to VS 2003 for building setup projects. You can use that to build setups for 1.0 framework projects. -- Phil Wilson [MVP Windows Installer] ---- [quoted text, click to view] "sprungli" <sprungli1@netscape.net> wrote in message news:OEXtA38pEHA.896@TK2MSFTNGP12.phx.gbl... > Thanks again, > > so this would mean I should revert to the scenario of my 1st post, since > there is just a check for the existance of the Framework, not an > installation option. Do you, by any chance, know if the .NET Framework > Bootstrapper accepts an URL path to the dotnetfx.exe? In this case I could > just set FxInstallerPath to the URL address where the dotnetfx.exe for > the1.0 version can be downloaded. It is difficult for me to test at this > time, that is why I am asking. > > Regards, > > s. > > > "Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message > news:e5TiKe8pEHA.3592@TK2MSFTNGP14.phx.gbl... > > Ok, I was looking at VS 2003 setup projects. VS.NET is slightly different, > > so all you have is the launch condition. I think that > MsiNetAssemblySupport > > *is* a launch condition that checks for the 1.0 framework. The > bootstrapper > > installs the Windows Installer engine, but the Windows Installer engine is > > installed when you install the framework. If the framework has been > > installled, you don't need a bootstrap, just the MSI file. > > -- > > Phil Wilson > > [MVP Windows Installer] > > "sprungli" <sprungli1@netscape.net> wrote in message > > news:OwhBPx7pEHA.3988@tk2msftngp13.phx.gbl... > > > Thank you Phil, > > > > > > The 1st option fits to my deployment needs. However, a .NET Framework > > > Launch > > > Condition is not included by default in the Launch Condition editor of > my > > > setup project(although there is a detected dependency) and when I try to > > > add > > > it manually, the new condition doesn't contain properties like > InstallUrl > > > or > > > SupportedRuntimes. Apart from the name it only has two props: Condition > > > (MsiNetAssemblySupport) and Message ([VSDNETMSG]). I guess this is not > the > > > NET Framework Launch Condition. Also what should be the value of the > > > Bootstrapper in this scenario? (My guess is Win Installer Bootstrapper.) > > > > > > Note: I am w/ VS.NET and the 1.0 Framework. > > > > > > > > > > > > "Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message > > > news:enYPoL2pEHA.708@tk2msftngp13.phx.gbl... > > >> A setup project has built in support for this. See: > > >> > > > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/vxgrfInstallUrlProperty.asp > > >> > > >> (I wouldn't *search* for a dotnetfx.exe on the client system anyway - > > >> this > > >> is the generic name for all the redistributable exe files for all the > > >> versions, so you could find the wrong one.) > > >> You can't write a custom installer class anyway - you can only run on > > >> MSI-based install at a time, and while yours is running the MSI-BASED > > >> dotnetfx won't run properly. This is also an option: > > >> http://www.codeproject.com/dotnet/dotNetInstaller.asp > > >> -- > > >> Phil Wilson > > >> [MVP Windows Installer] > > >> Definitive Guide to Windows Installer > > >> > > > > http://www.amazon.com/exec/obidos/tg/detail/-/1590592972/104-7044380-4696760 > > >> > > >> "sprungli" <sprungli1@netscape.net> wrote in message > > >> news:%23l$wkDypEHA.3396@tk2msftngp13.phx.gbl... > > >> > Hello, > > >> > > > >> > I plan to use the following installation scenario, involving the > sample > > >> > .NET > > >> > Framework Bootstrapper. > > >> > > > >> > 1. Ask the user to dowload the dotnetfx.exe from the Win Update site; > > >> > 2. Search for the dotnetfx.exe file on the client machine and if > found, > > >> > get > > >> > the path to it; > > >> > 3. Change Settings.ini (FxInstallerPath line) to point to this path; > > >> > 4. Start or instruct the user to click Setup.exe (the .NET Framework > > >> > Bootstrapper) - this would start the actual installation by checking > > >> > for > > >> > the > > >> > Framework and installing it, if not there, then doing the same for > > > Windows > > >> > Installer and, eventually, installing my application. > > >> > > > >> > The question is whether this can be acieved by a Setup project or I > > >> > need > > >> > to > > >> > write a custom Installer class? > > >> > > > >> > TIA > > >> > > > >> > > > >> > > >> > > > > > > > > > > > >
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 |