| Groups | Blog | Home |
dotnet setup : 2.0 .net framework redistributable setup
Is there any way to make the 2.0 redistributable setup not to install the whole thing if the target machine already has it? From the 1.1 and previous versions, if I run the setup and the machine already has it, it would go much, much faster, almost in few seconds, which makes me think that it checks for existing install and if it is up to date, does not overwrite it (which makes sense). However, with the 2.0 installation, it always takes forever (at least 3-5 minutes) to install even on machines that already have it. I tried to find documentation for the different install switches - found about silent install etc, but nothing about this. Does anyone have an idea what is happening? Thanks, Ivan
It doesn't install the whole thing again, so I'm not sure what you're
seeing. Typically setups that require the framework (such as MSI setups) are preceded by a launcher that checks to see if the framework is already installed - they don't attempt to launch it if it's already installed. It sounds like you're unconditionally installing it every time whether it's there or not. -- Phil Wilson [Microsoft MVP-Windows Installer] Definitive Guide to Windows Installer http://apress.com/book/bookDisplay.html?bID=280 [quoted text, click to view] <batvanio@gmail.com> wrote in message news:1143655488.811687.282610@j33g2000cwa.googlegroups.com... > Hi, > > Is there any way to make the 2.0 redistributable setup not to install > the whole thing if the target machine already has it? From the 1.1 and > previous versions, if I run the setup and the machine already has it, > it would go much, much faster, almost in few seconds, which makes me > think that it checks for existing install and if it is up to date, does > not overwrite it (which makes sense). > However, with the 2.0 installation, it always takes forever (at least > 3-5 minutes) to install even on machines that already have it. I tried > to find documentation for the different install switches - found about > silent install etc, but nothing about this. > Does anyone have an idea what is happening? > Thanks, > Ivan >
OK, Try the following:
1. Install the 1.1 .net framework redistributable (dotnetfx.exe) on a clean machine. 2. Install it again on the same machine and notice how long it takes the second time. 3. Now install the 2.0 .net framework redistributable (dotnetfx.exe) on a clean machine. 4. Install it again on the same machine and notice how long it takes the second time. 5. Now compare the results of steps 2 and 4. My experience is 8 sec. vs. 4 min. Also, unless you specify special cmd line switches, it will display the Repair or Uninstall dialog which is not very convenient if you want to include the redis. in your installer. This was not the case with 1.1. If you do specify the silent install switches though, then it probably install unconditionally the whole thing? I have seen this on all my attempts on several different machines. Thanks Ivan [quoted text, click to view] Phil Wilson wrote:
> It doesn't install the whole thing again, so I'm not sure what you're > seeing. Typically setups that require the framework (such as MSI setups) are > preceded by a launcher that checks to see if the framework is already > installed - they don't attempt to launch it if it's already installed. It > sounds like you're unconditionally installing it every time whether it's > there or not. > -- > Phil Wilson > [Microsoft MVP-Windows Installer] > Definitive Guide to Windows Installer > http://apress.com/book/bookDisplay.html?bID=280 > > <batvanio@gmail.com> wrote in message > news:1143655488.811687.282610@j33g2000cwa.googlegroups.com... > > Hi, > > > > Is there any way to make the 2.0 redistributable setup not to install > > the whole thing if the target machine already has it? From the 1.1 and > > previous versions, if I run the setup and the machine already has it, > > it would go much, much faster, almost in few seconds, which makes me > > think that it checks for existing install and if it is up to date, does > > not overwrite it (which makes sense). > > However, with the 2.0 installation, it always takes forever (at least > > 3-5 minutes) to install even on machines that already have it. I tried > > to find documentation for the different install switches - found about > > silent install etc, but nothing about this. > > Does anyone have an idea what is happening? > > Thanks, > > Ivan > >
1. Install the 1.1 .net framework redistributable (dotnetfx.exe) on a
clean machine. 2. Install it again on the same machine and notice how long it takes the second time. Why would you install the same thing again if you already installed it? I don't think that that is even possible.
Why are you installing it twice? You must be thinking that installing the
framework is some sort of simple file copy, but it's not. It uses MSI technology and yes, will go into repair mode just like many MSI setups do when you install the exact same MSI product file again. What happens if you try to install Visual Studio aagain? You'll see a similar Repair/Uninstall dialog. So check whether it's already installed before launching it. There's code here and the registry entries: http://support.microsoft.com/default.aspx?scid=kb;en-us;914135 -- Phil Wilson [Microsoft MVP-Windows Installer] [quoted text, click to view] <batvanio@gmail.com> wrote in message news:1143749858.538024.140880@u72g2000cwu.googlegroups.com... > OK, Try the following: > > 1. Install the 1.1 .net framework redistributable (dotnetfx.exe) on a > clean machine. > 2. Install it again on the same machine and notice how long it takes > the second time. > 3. Now install the 2.0 .net framework redistributable (dotnetfx.exe) on > a clean machine. > 4. Install it again on the same machine and notice how long it takes > the second time. > > 5. Now compare the results of steps 2 and 4. > > My experience is 8 sec. vs. 4 min. Also, unless you specify special cmd > line switches, it will display the Repair or Uninstall dialog which is > not very convenient if you want to include the redis. in your > installer. This was not the case with 1.1. > If you do specify the silent install switches though, then it probably > install unconditionally the whole thing? > > I have seen this on all my attempts on several different machines. > > Thanks > Ivan > > > Phil Wilson wrote: >> It doesn't install the whole thing again, so I'm not sure what you're >> seeing. Typically setups that require the framework (such as MSI setups) >> are >> preceded by a launcher that checks to see if the framework is already >> installed - they don't attempt to launch it if it's already installed. It >> sounds like you're unconditionally installing it every time whether it's >> there or not. >> -- >> Phil Wilson >> [Microsoft MVP-Windows Installer] >> Definitive Guide to Windows Installer >> http://apress.com/book/bookDisplay.html?bID=280 >> >> <batvanio@gmail.com> wrote in message >> news:1143655488.811687.282610@j33g2000cwa.googlegroups.com... >> > Hi, >> > >> > Is there any way to make the 2.0 redistributable setup not to install >> > the whole thing if the target machine already has it? From the 1.1 and >> > previous versions, if I run the setup and the machine already has it, >> > it would go much, much faster, almost in few seconds, which makes me >> > think that it checks for existing install and if it is up to date, does >> > not overwrite it (which makes sense). >> > However, with the 2.0 installation, it always takes forever (at least >> > 3-5 minutes) to install even on machines that already have it. I tried >> > to find documentation for the different install switches - found about >> > silent install etc, but nothing about this. >> > Does anyone have an idea what is happening? >> > Thanks, >> > Ivan >> > >
I don't want to install it twice, I am just describing a situation
where an installation is attempted when the client machine already has it. I don't want to bother with checking if the framework has been installed. This should have been done by the framework installer itself. What happens now is shifting the burden to client software which is probably caused by time pressure, or I don't know what but is never nice. And again, this was not the case with 1.1. [quoted text, click to view] Phil Wilson wrote:
> Why are you installing it twice? You must be thinking that installing the > framework is some sort of simple file copy, but it's not. It uses MSI > technology and yes, will go into repair mode just like many MSI setups do > when you install the exact same MSI product file again. What happens if you > try to install Visual Studio aagain? You'll see a similar Repair/Uninstall > dialog. So check whether it's already installed before launching it. > There's code here and the registry entries: > http://support.microsoft.com/default.aspx?scid=kb;en-us;914135 > -- > Phil Wilson > [Microsoft MVP-Windows Installer] > > <batvanio@gmail.com> wrote in message > news:1143749858.538024.140880@u72g2000cwu.googlegroups.com... > > OK, Try the following: > > > > 1. Install the 1.1 .net framework redistributable (dotnetfx.exe) on a > > clean machine. > > 2. Install it again on the same machine and notice how long it takes > > the second time. > > 3. Now install the 2.0 .net framework redistributable (dotnetfx.exe) on > > a clean machine. > > 4. Install it again on the same machine and notice how long it takes > > the second time. > > > > 5. Now compare the results of steps 2 and 4. > > > > My experience is 8 sec. vs. 4 min. Also, unless you specify special cmd > > line switches, it will display the Repair or Uninstall dialog which is > > not very convenient if you want to include the redis. in your > > installer. This was not the case with 1.1. > > If you do specify the silent install switches though, then it probably > > install unconditionally the whole thing? > > > > I have seen this on all my attempts on several different machines. > > > > Thanks > > Ivan > > > > > > Phil Wilson wrote: > >> It doesn't install the whole thing again, so I'm not sure what you're > >> seeing. Typically setups that require the framework (such as MSI setups) > >> are > >> preceded by a launcher that checks to see if the framework is already > >> installed - they don't attempt to launch it if it's already installed. It > >> sounds like you're unconditionally installing it every time whether it's > >> there or not. > >> -- > >> Phil Wilson > >> [Microsoft MVP-Windows Installer] > >> Definitive Guide to Windows Installer > >> http://apress.com/book/bookDisplay.html?bID=280 > >> > >> <batvanio@gmail.com> wrote in message > >> news:1143655488.811687.282610@j33g2000cwa.googlegroups.com... > >> > Hi, > >> > > >> > Is there any way to make the 2.0 redistributable setup not to install > >> > the whole thing if the target machine already has it? From the 1.1 and > >> > previous versions, if I run the setup and the machine already has it, > >> > it would go much, much faster, almost in few seconds, which makes me > >> > think that it checks for existing install and if it is up to date, does > >> > not overwrite it (which makes sense). > >> > However, with the 2.0 installation, it always takes forever (at least > >> > 3-5 minutes) to install even on machines that already have it. I tried > >> > to find documentation for the different install switches - found about > >> > silent install etc, but nothing about this. > >> > Does anyone have an idea what is happening? > >> > Thanks, > >> > Ivan > >> > > >
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 |