Skip to main content

Installing the .Net Framework 3.0 SP1 on Windows 2003 Server

I'm building an [automated] build server requiring the .Net 2.0 and 3.0 runtime. Unfortunately, at my client, they leverage a proxy server. The standard .Net 3.0 SP1 framework redist is really just a bootstrapper. Logged in as a local admin on the box, I didn't have the opportunity to authenticate the installation EXE with my domain credentials. So, the install kept timing out.

Finally, I found this helpful post from Aaron Ruckman on how to download the very elusive, full framework package. It's here, BTW (x86).

I finally get the full installation EXE downloaded to a fileshare, re-run the install and wham--"XPSEPSC: XPS must be installed..." Excuse you? This isn't an XPS...it's a VM.

I found a few MSDN posts here and here outlining the problem. I'm still not clear on what XPSEPSC does (Google yielded little) but you can download it here (x86). After installing XPSEPSC, the framework installed without issue.

Update:
Somewhat related, there is no .Net 3.0 SDK, perse. Because 3.0 is more an add-on to 2.0, the SDK remains [mostly] the same as detailed in this post. If you need specific 3.0 tools, look here.

Labels

Labels:

Comments

Anonymous said…
Thanks for those links, that standalone package was proving difficult to track down for a while ;)
Wednesday, April 02, 2008 11:39:00 PM
mpjames said…
haha - I ran the Microsoft Baseline Security Analyzer yesterday on a server, and it said I needed .net 3.0 SP1. The download link points to some MSXML update file instead. Finding the d/l link for the redistributable is near impossible, and then I needed the XPSEPSC thingie as well. BTW, it turns out to be a printer driver package - see http://www.microsoft.com/whdc/device/print/PrintDrv_redist.mspx
Wednesday, April 30, 2008 2:04:00 PM
Anonymous said…
Actually, the link you have posted for the redistributable .NET Framework 3.0 SP1 is for x64.

http://go.microsoft.com/fwlink/?LinkId=98106

will link to the file: NetFx30SP1_x64.exe

If you change the last digit in the LinkId to a 5 however,(so LinkId=98105) and paste it into your browser, you will get the NetFx30SP1_x86.exe file.

Hope this help some peeps out there.
Saturday, September 20, 2008 12:48:00 PM
Anonymous said…
Thanks for the link to the .net 3.0 sp1 x64. I couldn't find it on Microsoft's download site.
Wednesday, January 07, 2009 3:14:00 PM
Anonymous said…
In case someone else needs it, the x64 XPSEPSC prerequisite files are here: http://go.microsoft.com/fwlink/?LinkId=96333
Wednesday, January 07, 2009 3:35:00 PM
Unknown said…
I found it the x32 bit version full download
here it is
http://download.microsoft.com/download/8/F/E/8FEEE89D-9E4F-4BA3-993E-0FFEA8E21E1B/NetFx30SP1_x86.exe
Wednesday, July 29, 2009 2:56:00 PM
Post a Comment

Popular posts from this blog

TFS Reports Out of Date

You may have noticed it takes a while for Team Foundation Server (TFS) reports to reflect changes you've made to work items or builds. Let me guess...about an hour, right? Out of the box, TFS is set to refresh the data warehouse from its transactional store every 60 minutes. How do I change the frequency of the data warehouse refresh? Browse to the TFS Controller Web Service on your TFS application tier server within IE at: http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx Select the ChangeSetting option Enter RunIntervalSeconds for the settingId and the desired number of seconds for newValue (300 for 5 minutes...5*60) Select Invoke How do I force a data warehouse refresh? Two methods here: either via the above web service or using SQL Server Management Studio. Via the web service: Browse to the TFS Controller Web Service within IE at: http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx Select the Run option Click Invo...
6 comments
Read more

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki...
10 comments
Read more

VSTS Tester Demo Follow-ups

Last week, I delivered a VSTS 2008 Tester Edition demo to a prospective client. Following up on a few questions to which I didn’t know the answer: Q. Can I use Subversion with TFS? A. I get this question all the time from developers. It’s a perfectly valid question. The answer is no…but yes…sort of. The version control repository (and all data) must remain SQL Server. Yes, it’s proprietary. Further, if you plan to use TFS in your software development environment, but choose not to leverage it for version control, it severely limits the usefulness of the information elicited from TFS (because you’re not feeding in the crucial VC data). If you’re not leveraging VC in TFS, you’re probably not leveraging Team Build either. That said, while a fully-integrated TFS for ALM and SCM is the ideal, there’s a compelling argument to leverage TFS as a repository for requirements, scenarios, test cases, functional and load testing as well as defect tracking. TFS is an excellent repository to s...
2 comments
Read more