Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

Updated VS bootstrapper packages for .NET Framework 2.0 SP2 and 3.0 SP2 with post-SP2 GDR included

Updated VS bootstrapper packages for .NET Framework 2.0 SP2 and 3.0 SP2 with post-SP2 GDR included

  • Comments 5

This week, new Visual Studio 2008 bootstrapper packages were released for the .NET Framework 2.0 SP2 and the .NET Framework 3.0 SP2.  These packages are updated versions of the packages released last fall that I described in this blog post.  They contain the following changes:

  • The updated 2.0 SP2 bootstrapper package includes the installer packages for 2.0 SP2 and the update for 2.0 SP2 (KB958481), and it will chain both of these packages during the install process if they are not yet installed on the target system.
  • The updated 3.0 SP2 bootstrapper package includes the installer packages for 3.0 SP2 and the update for 3.0 SP2 (KB958483), and it will chain both of these packages during the install process if they are not yet installed on the target system.
  • The packages are now available in all Visual Studio languages.
  • The packages now support both x86 and x64 processor architectures.

Here are some links for the updated .NET Framework 2.0 SP2 and 3.0 SP2 bootstrapper packages for VS 2008:

There are a few caveats to keep in mind when using the updated .NET Framework 2.0 SP2 and 3.0 SP2 bootstrapper packages:

  • They only support installing on Windows XP and Windows Server 2003.  You cannot use them on Windows Vista or Windows Server 2008.  If you need to install the .NET Framework 2.0 SP2 or 3.0 SP2 on Vista or Windows Server 2008 as a part of your application installer, you should use the .NET Framework 3.5 SP1 bootstrapper package that is included with Visual Studio 2008 SP1 instead.
  • They do not support the "Download components from the component vendor's web site." option.  This means when you build your installer and include one of these bootstrapper packages, you will see build warnings about the HomeSite attribute, and the full contents of the .NET Framework 2.0 SP2 and/or 3.0 SP2 installers will be included next to setup.exe in your build output.  If you would prefer to have download-on-demand functionality for the .NET Framework in your setup, then you should use the .NET Framework 3.5 SP1 bootstrapper package instead.
  • Thank you for submitting this cool story - Trackback from DotNetShoutout

  • With regard to the .NET 2.0 SP2 bootstrapper, you wrote "They do not support the Download components from the component vendor's web site" option. Is there any technical reason why I can't put the bootstrapper on my own web site and then instruct the deployment project to get the file from my own distribution URL? If it is so simple, why doesn't Microsoft support this? I could test it own but I have no confidence that if it works for me that it will also work for my customers.

    I recently upgraded from VS 2008 to VS 2010 and my deployment project broke because the old .NET 2.0 bootstrapper - perhaps pre-SP2 - which did support the download-on-demand option, is not included and I can't seem to find it anywhere. Even though my application only requires .NET 2.0, I've considered using the 3.5 Client Profile but there are scenarios where this will cause a much larger download than I had before.

  • Hi Justinm - Yes it should be technically possible to host this package on your own server.  I didn't work on the team that made the decision to not support the "Download components from the component vendor's web site" option, so I don't know the reason why they were not made available.

    You should be able to copy the old pre-SP2 .NET Framework 2.0 bootstrapper package from your VS 2008 install location to the VS 2010 install location and use it from within VS 2010 if needed.  The VS 2008 location for these packages is %ProgramFiles%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages, and the VS 2010 location is %ProgramFiles%\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages.

    There are some technical limitations in the 3.5 Client Profile that would lead me to not recommend that you use it (it only works on Windows XP, and it only allows the install of client bits on a machine that doesn't have any part of the .NET Framework 2.0/3.0/3.5 stack installed - otherwise you get a full 3.5 SP1 install anyways and you don't gain any download size savings).

  • Here is an example for Bootstrapper Package - Microsoft .NET Framework Version 2.0 Redistributable

    under Visual Studio 2010

    mdb-blog.blogspot.com/.../bootstrapper-package-visual-studio-2010.html

  • justinm, "Download prerequisites from the component vendor's web site" means downloading them from Microsoft's web site.

    Your question rather regards the "Download prerequisites from the same location as my application" option that is supported (at least because it is not stated otherwise).

Page 1 of 1 (5 items)
Leave a Comment
  • Please add 5 and 2 and type the answer here:
  • Post