Repeated conversion of project file - by Ricomyer

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 334842 Comments
Status Closed Workarounds
Type Bug Repros 5
Opened 3/27/2008 10:39:46 AM
Access Restriction Public

Description

Each time I open our project file, it comes up with 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."

We just converted our web application project from VS.net 2005 to VS.net 2008.  We are using VSS with it.  After this message, the project file is not checked out and nothing seems to have changed.
Sign in to post a comment.
Posted by gatisb on 12/2/2010 at 1:42 AM
The same issue applies for VS 2010, when project converted from 2003 to 2010
Posted by Microsoft on 4/24/2008 at 8:10 AM
Thanks for the report, and sorry to hear you're experiencing this problem. Due to architectual issues, this is a very difficult issue to fix for this release. However there is a workaround you can use to get rid of that dialog:

1. For the project that's causing you the issue, backup your solution file, your project file, and the "hint" file associated with your project file (the .vspscc file sitting in the same directory as your project) to some other location.
2. Check out your solution file and the project file and close VS
3. Open the project hint file (.vspscc) in notepad, change the ENLISTMENT_CHOICE from COMPULSORY to "ENLISTMENT_CHOICE" = "NEVER"
4. Open your solution file in notepad, remove that line SccProjectEnlistmentChoiceX = 2 (X is the number that corresponds to your project that is causing you the problem). Also, if you see the line "SccWebProjectX=true" (x is again the number of the project in your solution), remove that as well.
5. Open everything in VS again, and assuming everything works now, check in your files.

If this does not work or causes you other problems, feel free to reactivate this issue.

Thanks,
-The Visual Web Developer Team
Posted by Microsoft on 3/28/2008 at 12:54 AM
Thanks for your feedback. We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team