Microsoft Knowledge Base Email Alertz

KBAlertz.com: When you try to merge solution files that contain a project or projects that are under source code control, you may receive the following error message:

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 317523 - Last Review: February 23, 2007 - Revision: 1.1

PRB: "Only One Database Connection at a Time Is Supported" Error Message When You Merge Source Controlled Solution Files in Visual Studio .NET IDE

This article was previously published under Q317523

On This Page

SYMPTOMS

When you try to merge solution files that contain a project or projects that are under source code control, you may receive the following error message:
Only one database connection at a time is supported

CAUSE

This problem occurs because the projects in each solution are stored in different databases. Only one Visual SourceSafe database is supported in a solution. Even when you use the same database, this problem occurs if one database is identified with a Universal Naming Convention (UNC) path and the other database is identified with a regular file path.

RESOLUTION

To work around this behavior, use one of the following methods.

Workaround 1

Leave the project files in separate solution files.

Workaround 2

Move one solution into the same database as the other database when you merge the solutions. To do this, follow these steps:
  1. Open the first solution in Visual Studio .NET.
  2. On the File menu, point to Source Control, and then click Change Source Control.
  3. In the Change Source Control dialog box, unbind the solution from its source control database.
  4. Open the second solution in Visual Studio .NET.
  5. On the File menu, point to Open, and then click Project.
  6. Click Add to Solution, and then open the first solution.
  7. Check in the project file that you just added. You are prompted to add this project to the same database as the solution that it is being added to.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce the Behavior

  1. Create a new project in Visual Studio .NET.
  2. On the File menu in the Visual Studio .NET IDE, point to Source Control, and then click Add Solution to Source Control.
  3. Close the solution.
  4. Create another new project in Visual Studio .NET.
  5. Add the second solution to source control, and use a different Visual SourceSafe database, or use the same database but specify a UNC path instead of the file path to the database.
  6. On the File menu in the Visual Studio .NET IDE, point to Open, and then click Project.
  7. In the Open Project dialog box, click Add to Solution, open the solution that you created in step 1, and then click Checkout.

REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
307467  (http://kbalertz.com/Feedback.aspx?kbNumber=307467/EN-US/ ) HOW TO: Create an ASP.NET Application from Multiple Projects for Team Development

APPLIES TO
  • Microsoft Visual SourceSafe 6.0C, when used with:
    • Microsoft Visual Studio .NET 2002 Professional Edition
    • Microsoft Visual Studio .NET 2002 Enterprise Architect
    • Microsoft Visual Studio .NET 2002 Enterprise Developer
    • Microsoft Visual Studio .NET 2002 Academic Edition
Keywords: 
kbprb KB317523
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please