Search

"File > Source Control > Go Online" causes the IDE to open all data connections in server explorer by rami_

Closed
as Duplicate Help for as Duplicate

6
0
Sign in
to vote
Type: Bug
ID: 585566
Opened: 8/11/2010 12:10:16 PM
Access Restriction: Public
0
Workaround(s)
5
User(s) can reproduce this bug
If I open a solution that is offline (TFS 2010 is down for example) and then click on "File > Source Control > Go Online" when the TFS server is back online, it causes the IDE to automatically open all data connections in server explorer and enumerate its child nodes.
Details (expand)

Visual Studio/Silverlight/Tooling version

Visual Studio 2010

What category (if any) best represents this feedback?

 

Steps to reproduce

1. Create a vs2010 solution that is source control bound to tfs 2010

2. add a few database connections in the vs2010 server explorer window and then disconnect.

3. close the solution

4. Add an entry in your hosts file that maps the tfs 2010 server host name to an unused ip address to simulate source control offline mode.

5. Open the solution.

6. Click OK on the dialog
Go Offline
The Team Foundation Server http://tfs2010:8080/tfs/defaultcollection is currently unavailable.
This solution will be opened offline.

7. Remove the entry previously created in your hosts file

8. Click on "File > Source Control > Go Online"

Notice that the data connections are now connected and child nodes expanded

Product Language

English

Operating System

Windows 7

Operating System Language

English

Actual results

One of the child like "Database Diagrams" gets automatically expanded and this can causes unexpected behavior such as the following:
1. if there are no db diagrams, the message box will appear "This server does not have one or more of the database object required to use database diagramming. Do you wish to create them?"
2. if the database server is unavailable, the message box will appear:
"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connects. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"
3. After all message boxes are dismissed, the server explorer window is unresponsive.

Expected results

"File > Source Control > Go Online" should not automatically open and enumerate nodes of database connections in the server explorer window.
File Attachments
0 attachments
Sign in to post a comment.
Posted by beauXjames on 5/4/2011 at 8:06 AM
With existing projects, when I attempt to go online, the same error occurs for each Team Project that is part of a Collection until it reaches the project I am attempting to go online with. Once the series of connections reaches the project in question, pending changes are noted and resolved. There is no way to access the 'Pending Changes Tool Window' until this operation completes successfully, for the application is frozen.

When 'Filter by Solution' is clicked in the associated window, it appears as though only changes to the active solution are shown...which is good, however I am not certain that it will resolve the issue of going back online.
Posted by Microsoft on 8/25/2010 at 2:10 PM
Thank you for reporting this problem. It's caused by a combination of "Filter by solution" feature turned on in Pending Changed Tool Window and database connections existing in server explorer. As a workaround please turn off "Filter by solution" option in Pending Changes Tool Window. This bug will be fixed in future version of Visual Studio.
Posted by Microsoft on 8/17/2010 at 3:05 AM
Thank you for reporting the issue.
We are routing 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/11/2010 at 6:22 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.