After I have manually converted a solution to using the Web Application Project, I get the following two errors when I open the solution.  The first is soon after the solution is opened :

 "The following Web projects must be converted to the new Web Site Format. The con....."

The second error is just before the solution is ready to open:

"Some of the properties associates with the solution could not be read." 

VS 2005 does not actually seem to do anything with the project or solution file.

Any ideas about what I should do to eliminate these errors?

Best regards,

Metro.

With the new RC1 drop you should not need to manually convert your solution or project file.  After downloading and installing RC1 simply open the VS03 solution in VS05.  It will automaticaly convert it to a Web Application Project.

If you're already doing this and still getting this error please let me know.

Thanks, Brad.

I have figured out what was generating the error messages when I load my solutions that contain Web Application Projects.  I had done a manual conversion for reasons that I will explain in a separate post.  In addition to the directions in Scott Guthrie's post, (since our projects are all in scc) I needed to convert the SCC configuration for the projects to conform to a "Local" (as opposed to "Web") project.

Well, I either made mistakes when changing the configuration, or VS 2005 re-wrote the configuration when I loaded the project, because the scc entries were definitely messed up.  It had the web application projects one directory deeper in the tree than they actually are.  Once I corrected the entries, the projects loaded fine, without error.

As an aside, why in the world is the solution file not xml?

Best regards,

Metro.

I get the first message constantly when I open my WAP projects and I used the RC1 conversion wizard. Here's the message:

"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."

It doesn't appear to do any such thing when it opens though. Any clue as to why this would be happening and how I can stop it?

TIA,
Drew

We had a similar problem.  Take a look at your .csproj.vspscc file.

Our old version:

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

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

The way I figured this out was to take the source code to our entire project, manually remove the Visual SourceSafe bindings, then add it to source control.  Then I did a diff on the two directory trees, noting the differences in all files.