Search

After install TFS 2010 requires .Net FW 3.5 (FW 4.0 already installed) by alexbirk

Closed
as By Design Help for as By Design

3
0
Sign in
to vote
Type: Bug
ID: 585754
Opened: 8/12/2010 6:46:37 AM
Access Restriction: Public
0
Workaround(s)
1
User(s) can reproduce this bug
I successfully installed VS 2010 and TFS 2010 (Build Server feature only) on clear Win 2008 R2 server. After then i start configuring build agent and build controller, but in "TFS Build Service Configuration Wizard" i get error "The .Net 3.5 Framework is not installed. You must install the .Net 3.5 Framework feature before continuing."

Why needed FW 3.5, when already installed FW 4.0? TFS & VS already install on server .Net FW 4.0.
If TFS requires FW 3.5, why it not installed by TFS setup?
Details (expand)

Visual Studio/Silverlight/Tooling version

Team Foundation Server 2010

What category (if any) best represents this feedback?

 

Steps to reproduce

1) Get clear virtual machine.
2) Install Windows 2008 R2 x64
3) Install all latest Windows Update
4) Install Visual Studio 2010 Premium
5) Install TFS 2010 (Build Server feature)
6) Start "Build Service Configuration Wisard" and configure Build Agent and Build Service.

Product Language

English

Operating System

Windows Server 2008 R2

Operating System Language

English

Actual results

"Build Service Configuration Wizard" on page "Readiness Chacks" you give error "The .Net 3.5 Framework is not installed. You must install the .Net 3.5 Framework feature before continuing."

Expected results

"Build Service Configuration Wizard" must successfully configure Build Server with FW 4.0.
File Attachments
0 attachments
Sign in to post a comment.
Posted by T G Wilson on 12/27/2011 at 1:59 PM
Was this closed without a solution or workaround? I'm having the same problem. This really needs a response.
Posted by Microsoft on 9/7/2010 at 10:16 AM
Unfortunately, the TFS code to install 3.5 does not work correctly on Server 2008 R2 (because 3.5 is available as a Feature or Role on this server, rather than being a separate install). When we discovered this, we chose to block during configuration and point to the OS feature, rather than re-work the feature that adds 3.5 on the other OSes.

We are looking at making the experience more consistent for the next release.
Posted by Microsoft on 8/12/2010 at 8:37 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 8/12/2010 at 6:06 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.