Oh boy, this one has been *killing* me and my team.  In Visual Studio 2005 SP 1, we converted a couple of old VS 2003 projects into the new Visual Studio web projects.  After conversion, though, we continued to get the following error:

The following Web projects must be converted to the new Web Site format. The conversion process will remove all source control bindings and the project will not be under source control after migration.

xxxxx.csproj

Source Control Error message

It turns out that there are 2 files that need to change to fix this little error.  The first is the Project_Name.csproj.vspscc file (*.vspscc).  This file will look something like this:

""
{
"FILE_VERSION" = "9237"
"ENLISTMENT_CHOICE" = "COMPULSORY"
"PROJECT_FILE_RELATIVE_PATH" = ""
"NUMBER_OF_EXCLUDED_FILES" = "0"
"ORIGINAL_PROJECT_FILE_PATH" = "http://localhost/WebApplication1/WebApplication1.csproj"
"NUMBER_OF_NESTED_PROJECTS" = "0"
"SOURCE_CONTROL_SETTINGS_PROVIDER" = "PROVIDER"
}

Change the line ENLISTMENT_CHOICE from COMPULSORY to NEVER, and remove the value from inside of the ORIGINAL_PROJECT_FILE_PATH variable.  The new file will look like this:

""
{
"FILE_VERSION" = "9237"
"ENLISTMENT_CHOICE" = "NEVER"
"PROJECT_FILE_RELATIVE_PATH" = ""
"NUMBER_OF_EXCLUDED_FILES" = "0"
"ORIGINAL_PROJECT_FILE_PATH" = ""
"NUMBER_OF_NESTED_PROJECTS" = "0"
"SOURCE_CONTROL_SETTINGS_PROVIDER" = "PROVIDER"
}

Next, open the .sln file in a text editor.  Look for the following line:

SccProjectEnlistmentChoicexx = 2

Where xx is the project number.  One only needs to search for the text SccProjectEnlistmentChoice to find the line(s) in the solution file.  Now, remove the entire line that contains the SccProjectEnlistmentChoice text.

Save both files, and re-open the solution.  That should clear out that pesky error message!

Advertisements

5 thoughts on “How to fix the error ‘The following Web Projects must be converted to the new Web Site format’ message when the project is already converted

  1. Thanks, this saved a lot of headache 🙂 The project was still working, but the error message was really annoying and sort of alarming.

  2. Thank you for this. It just fixed the exact same problem in a Visual Studio 2013 project that was being upgraded from VS 2003.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s