Working with Visual Studio.NET


Putting additional Visual Studio.NET projects under Code Co-op control


After your Visual Studio.NET solution is under version control, you might add new Visual Studio.NET projects to it. To add these projects to your Code Co-op project, it's simplest to let Visual Studio.NET add it for you. And to make it easy to see which files are being added and changed, it's best not to have other files in the project checked out when you are adding a new project to version control.

Your new Visual Studio.NET project is now fully integrated with your Code Co-op project. You can open the solution in Visual Studio.NET and get to work.


Opening a Code Co-op project in Visual Studio.NET

If you joined a Code Co-op project that was already integrated with Visual Studio.NET you do not have to do anything in order to integrate. You can just open the solution in Visual Studio.NET (an easy way to do this within Code Co-op is to right click on the .sln file and select Open with Shell) and you can start working with it immediately.


Renaming Solutions

Renaming a solution in Visual Studio.NET can cause problems and is not recommended. If you must rename a solution, here's a sequence that will work. In this example, we're renaming a solution from Original to KillerApp:

  1. In Code Co-op, check out Original.sln and Original.vssscc
  2. Start Visual Studio.NET and open the solution.
  3. Right click on the solution item (at the top of the Solution Explorer window), select Rename and enter the new name.
  4. If a warning dialog appears, click Continue with Change
  5. Close the solution
  6. In Code Co-op, go to the Check-in Area tab and Un-CheckOut Original.sln and Original.vsscc (the files you checked out in step #1)
  7. Go to the Files tab and Delete Original.sln and Original.vsscc
  8. Select KillerApp.sln and KillerApp.vsscc, click on the Selection menu and select Add To Project
  9. Go to the Check-in Area tab, select KillerApp.sln and KillerApp.vsscc and check them in.
You have now successfully renamed your Visual Studio.NET solution.
 

Upgrading from Visual Studio 6.0 to Visual Studio.NET with sub-projects


Upgrading from Visual Studio 6.0 to Visual Studio.NET may produce binding errors if you have sub-projects in VS 6.0. Before outlining the solution, keep in mind that VS.NET organizes development into two layers:

To fix the integration with VS.Net, do the following:

Visual Studio.NET Web Solutions and Code Co-op Control


VS.NET treats Visual Basic , Visual C# and Visual J# Web Solutions in a special way. Adding them to source control requires an additional change in VS.NET configuration. Also the process of joining a Web Solution differs from a standard procedure and has its own specific requirements.
Note: You do not have to do any of these for Visual C++ Web Solutions.

Before you create a Web Solution you must set the VS.NET default project directory to point to your system's default web publishing folder (usually "c:\inetpub\wwwroot"). To do this, open the Options dialog from the VS.NET Tools menu and change the default directory in the Environment.Projects and Solutions section.

Joining an existing Web Solution on the same computer more than once is essentially impossible.

When joining an existing Web Solution from other computers you must be aware of the following requirements:

After you joined an existing Web Solution you will be initially unable to open the solution in VS.
You will need to ask the sender of the Full Sync to send you a copy the ".suo" file. Do not add this file under Co-op's control! The .suo file is a VS file and is placed in the root folder of the solution. The sender might not see the .suo file in the explorer if s/he does not have "show hidden files" option set (it has the Hidden attribute). But the sender can always see the .suo in Code Co-op's display and drag and drop it to an e-mail message.

By the way, make sure you add ".webinfo" files under Co-op's control. VS does not add them by default when Adding Solution to Source Control.