.NET Framework 3.5, 3.0 SP1 & 2.0 SP1 Language packages

Recently the .NET Framework 3.5 Language packages were released.  You can get them by going to the following Microsoft Download center details page. 2.0 x86 — http://www.microsoft.com/downloads/details.aspx?FamilyId=5F7F4632-C9C0-4E79-B269-C2AEE9D1962E&displaylang=en 2.0 x64 – http://www.microsoft.com/downloads/details.aspx?FamilyId=1CC39FFE-A2AA-4548-91B3-855A2DE99304&displaylang=en 2.0 ia64 – http://www.microsoft.com/downloads/details.aspx?FamilyId=DE4DFCCD-E75F-4C2F-9991-565A69AF9015&displaylang=en 3.0 — http://www.microsoft.com/downloads/details.aspx?FamilyId=B3E05715-4D28-4C18-9A60-E26C0E3FFE1E&displaylang=en 3.5 — http://www.microsoft.com/downloads/details.aspx?FamilyID=c78987b9-97f4-455f-bee7-f6bfa4ad774e&DisplayLang=en   After you browse to the page then you will need to choose a…


.NET Framework 3.0 SP1 & 2.0 SP1 on Vista RTM?

I’ve received the following type of question a few times and would like to give the answer with some background: Q. Where is the .NET Framework 3.0 SP1 & 2.0 SP1 for Vista RTM? A. .NET Framework 3.0 & 2.0 released with Vista as OS Windows Components, which means that they are serviced as any…


Recent .NET Framework KBs enumerated

With .NET Framework 3.5 on Vista or LHS you might get one of the following KBs installed.  The following table helps to identify which KB matches what Framework version and which language. LCID = Language Code ID. NetFx2.0 SP1 & NetFx3.0 SP1 = These KBs are the representation for the Language enabling packages.  The English…


.NET Framework 3.0 or 3.5 installation will fail if the Print Spooler is not running on Windows XP or Windows Server 2003

One of the .NET Framework 3.0 or 3.5 prerequisite packages requires that the Print Spooler service is running in the “Started” State. If the Print Spooler Service is not running, the .NET Framework 3.0 or 3.5 installation will fail. To resolve this issue   Start the Print Spooler service before you install the .NET Framework….


Creating .NET Framework 3.0 SP1 redist

Please follow the official guidelines at http://msdn.microsoft.com/en-us/library/cc160716.aspx


.NET framework 3.0 SP1 & 3.5 download managers

.NET Framework 3.0 SP1 & 3.5 released with a small webdownload, which then manages the installation of .NET Framework across all supported OS and architectures. This Blog will explain what they are and how to use them in your role as an end-user, Administrator and ISV. For End Users, we expect that you will get the .NET…


What to do when you go to post a setup and deployment issue on the MSDN forums?

Step 1. It would be super helpful if you could provide the following information at the beginning of your post: Version of .NET Framework you are trying to install. Where did you get it (web page, path, application that redistributed the framework) Is this a pre-release, CTP or beta version? Which? (Beta#, CTP (Month Year), RC,…


.NET Framework 3.5 Installation validation tool

If you want to detect if your .NET Framework 3.5 installation was successful, you can use this tool to verify that the right versions are installed. Instructions: 1. Download the following file to your computer: http://cid-e7f319723234fb5c.skydrive.live.com/self.aspx/Public/netfx35tools/NetFx35_detect_issues.bat 2. Open a command prompt by doing start -> run and type cmd. 3. enter the full path to…


.NET Framework 3.5 RTM Detection Logic.

When you install .NET Framework 3.5, it installs .NET Framework 3.0 SP1 & .NET Framework 2.0 SP1, or equivelent cumulative update on Vista.   For 3.5 RTM we look for the following: Registry Key Name Value HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ NET Framework Setup\NDP\v3.5 Name: Install Type: DWORD Data: 1 For 3.0 RTM see the following: http://msdn2.microsoft.com/en-us/library/aa964978.aspx#DetectingTheMicrosoftDotNETFramework3_0   For…


When I try to download .NET Framework 3.0 GOLD my computer says that this isn’t a Windows 32 application.

Commonly this is caused by the installation program you’ve downloaded to become corrupted in the download. By redownloading to either a different location you should be able to fix this issue.  Another common remedy for this issue is to download the redistributable package corresponding to your architecture: To download the full redistributable package, rather than…