» Support » Knowledge Base » All Perforce Applications » Integrations - Perforce » P4SCC (Visual Studio) » Perforce With Visual...

Perforce With Visual Studio .NET

Integrate Perforce with Visual Studio .NET

This article talks about specifics you need to know when using the P4SCC plugin with Visual Studio .NET.

Version Compatibility

The following versions of Visual Studio support version control:

Any version not listed does not support version control.

Which version of the Perforce SCC plug-in to use

Always use the most recent build. See the Release Notes for details.

Visual Studio file types

Below is the list of the most common types of Visual Studio files:

File Extension	Description
.actproj	ACT project
.atp	ACT project
.csproj	Visual C# project
.dbp	Database project
.dmp	Crash Dump project
.dsp	Project Converter
.dsw	Visual Studio Workspace
.etp	Enterprise Template project
.exe	EXE project
.hwproj	Microsoft Help project
.mdmp	Crash Dump project
.mdp	Project Converter (VC 4.x)
.sln	Solution
.vbproj	Visual Basic project
.vcproj	Visual C/C++ project
.vdp	Setup and Deployment project
.vdproj	Setup and Deployment project
.vsmacros	Binary based macro project
.vsmproj	Unicode based macro project
.opt	Source Code Control related
.suo	Source Code Control related
.vssscc	Source Code Control related
.vcproj.vspscc	Source Code Control related
.csproj.vspscc	Source Code Control related
MSSCCPRJ.SCC	Source Code Control related. Perforce is responsible for the content of this file. This file must never be added to Perforce.

Good to know ...

Do not put the .suo files (user preferences) in Perforce. .NET will automatically add .vsscc, vssscc and .vspscc files to Perforce if needed. In general, leave it up to your IDE whether or not to check certain source control specific files into Perforce.
Always add Visual Studio files to Perforce from within the Visual Studio IDE. If you need to bind the files to Perforce from within Visual Studio manually:
1. Load the project into .NET
2. Choose File>Source Control>Change Source Control.
3. Highlight the solution and project files.
4. Choose Bind.
5. Click OK.
After you have completed these steps, you should be able to check the files in and out. You can also use the above method if you need to re-connect your .NET Project with Perforce.

In Perforce, add is a two-step process, while Visual Studio expects "auto-add". To add a file to an existing solution in Visual Studio .NET:
1. To open a file for add, choose Add New|Existing Item.
2. To submit a file, select the file and choose Check In Now.
To see which files are open for add, choose Show Pending Checkins.
Always Use Visual Studio .NET for Source Control Operations

Use a Single Solution Model whenever possible. The Single Solution Model uses one .sln file as a container for all of the projects defined by your application

Use a Consistent Folder Structure for solutions and projects. Ideally, keep solution files in the top directory and all of the projects in subdirectories.

To map a project from another machine/location after your initial sync, choose File->Source Control->Open from Source Control. This command updates the files with the new user and workspace attributes during an implicit bind. The first time you do this, you must enter the full path to the solution file.

For further information on the Perforce SCC Plug-In, see:

40 users have rated this article 1.8 out of 5