Why Visual Studio 2005 ask me to convert a solution already got converted

By kdeschenes ·
Somebody did the conversion of a solution from .net 1.1 to .net 2.0 by using the automatic conversion wizard of Visual Studio 2005. Then, he changed to another company.
Now, I take over his job. Unfortunately, when I attempted to open that solution, Visual Studio 2005 prompted me the conversion wizard again to forced me to perform a conversion on the solution. Does someone know why?


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

All I can say is I haven't had a similar problem

by Tony Hopkinson In reply to Why Visual Studio 2005 as ...

Are you sure he saved the converted project and that you have'nt got the original. Also did it successfully convert.

Bit obvious I know..

As far as I know it just looks at some waffle inside the sln file.
Which version of 2005 are you using. If it's Orcas it could be doing an other conversion to .Net 3 or 3.5.

Collapse -

Why a re-conversion ... ?

by hercules.gunter In reply to Why Visual Studio 2005 as ...

I would suggest converting, saving, shutting down and opening the saved file. If it doesn't want to convert again, don't worry about it. Sometimes you just have to accept a quirky outcome and move on.

Related Discussions

Related Forums