Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
Back when the .NET Framework 3.5 beta 2 was released, I posted this item on my blog describing how to download the individual pieces of the .NET Framework 3.5 beta 2 in order to create an installable layout that can be used to create an installer that includes the .NET Framework 3.5 or for network deployment. If you have looked at those instructions, you'll notice how long, tedious and potentially error-prone they are.
Fortunately, as Bret Grinslade noted in this blog post, in the final release of the .NET Framework 3.5, a new package is available for download that includes all of the pieces of the .NET Framework 3.5 so that you no longer need to download the pieces individually in order to assemble an installable layout.
The combined installation package for the .NET Framework is available for download at http://download.microsoft.com/download/6/0/f/60fc5854-3cb8-4892-b6db-bd4f42510f28/dotnetfx35.exe.
After downloading this package, you can extract the contents by running dotnetfx35.exe /x and it will prompt you with a location to extract the contents to. From there, you can trim down the installer payload if appropriate in your deployment scenario in the following ways:
Now you can run dotnetfx35setup.exe from the extracted folder to start installing the .NET Framework 3.5.
One important note - if you decide to optimize your installer payload using any of the suggestions above, and it turns out that you over-optimized and setup really does need one of the packages that you deleted from the extracted folder, then .NET Framework 3.5 setup will attempt to automatically download the package for you if you have a live Internet connection during setup. If it needs to download a package and the system does not have a live Internet connection, then .NET Framework 3.5 setup will fail to install.
A little while ago, I posted this item on my blog that describes a potential issue when installing the
Is it possible to generate a log from dotnetfx35setup.exe? tried /l*v <log file> no joy. Any suggestions?
Hi GHardie - As I described in the blog post at http://blogs.msdn.com/astebner/archive/2008/02/27/7927123.aspx, the .NET Framework 3.5 setup creates its own set of verbose logs by default, so there is no need to pass any additional logging switches or set any of the standard Windows Installer logging policies.
You should be able to find the logs from this setup by using the list at http://blogs.msdn.com/astebner/archive/2007/07/31/4156781.aspx.
Hopefully this helps.
PingBack from http://www.itwriting.com/blog/?p=620
The setup program for the .NET Framework 3.5 and the Visual Studio 2008 Express Editions contains logic
PingBack from http://www.hanselman.com/blog/SmallestDotNetOnTheSizeOfTheNETFramework.aspx
There's been some confusion about the size of the .NET Framework. The .NET Framework is not really
There's been some confusion about the size of the .NET Framework. The .NET Framework is not really a
PingBack from http://radonr.jyartonline.com/2009/06/25/installing-net-35-framework-without-internet/