Home Dashboard Directory Help
Search

"Object reference not set to an instance of an object" when connecting to TFS 2008 server using VS 2012 Update 2 CTP 3 by Brian Baker


Status: 

Closed
 as Duplicate Help for as Duplicate


5
0
Sign in
to vote
Type: Bug
ID: 779726
Opened: 2/21/2013 9:55:11 AM
Access Restriction: Public
0
Workaround(s)
view
4
User(s) can reproduce this bug

Description

After installing VS 2012 Update 2 CTP 3, I can no longer connect to my TFS 2008 server using Team Explorer.

When VS starts up, the Team Explorer pane shows the "Connect to Team Foundation Server" link. I click that and get the connection dialog, which properly lists all the team projects on my server. However, once I click Connect, I get an error dialog reading:

---------------------------
Microsoft Visual Studio
---------------------------
Object reference not set to an instance of an object.
---------------------------
OK
---------------------------

Connecting to a TFS 2010 or TFS 2012 server works ok.
Details
Sign in to post a comment.
Posted by WPFGod on 5/17/2013 at 8:16 AM
This is still happening with the current Update 2 released.... These kinds of things are really killing my development teams productivity. Its like 100 bugs were in VS2012 and when we install updates it is just a new list of bugs we get from installing new updates. I am losing my confidence in updates for this product... :(
Posted by Brian Baker on 3/7/2013 at 1:43 PM
Confirmed fixed in CTP 4.
Posted by Microsoft on 2/27/2013 at 9:04 AM
Thanks for reporting this issue. We found this bug internally, and have already fixed it. You'll see the update in the next Update 2 CTP.

Thanks,
Matt
Program Manager | TFS Version Control
Posted by Microsoft on 2/21/2013 at 11:38 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 2/21/2013 at 2:54 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.