Re: Converting VC6 Project to VS2005 - Warning Message

I had been opening the project from the start page, which apparently
defaulted to opening it with the .dsw file. Once I ignored the start page
and opened the project directly using File|Open|Project/Solution and
selected the .sln file, the start page opened it without the warning. Thanks
asm23.

As far as I can tell, V2005 doesn't write to the .dsp file at all, and
therefore does not make it unusable by previous versions of Visual Studio as
the warning suggests.

Am I correct, therefore, to conclude that the warning is incorrect by saying
you will not be able to edit the project in previous versions of Visual
Studio? Am I correct by saying you CAN edit the project in VC6 (changing
the .dsp file), and use it with VS2005 as long as you subsequently open the
project with the .dsw file?


"asm23" <asmwarrior@xxxxxxxxx> wrote in message
news:gc3qne$b2f$1@xxxxxxxxxxxxxxxx
AVee wrote:
When opening a VC6 (MFC) project in VS2005 I get the following warning,

"The project 'MyAppp.dsp' must be converted to the current Visual C++
project format. After it has been converted, you will not be able to edit
this project in previous versions of Visual Studio. Convert and open the
project?"

This warning appears each time I open the project with VS2005, and
contrary to the warning I have found that I am indeed able to edit the
project with VC6.

I am hoping that someone can explain why this warning appears, why it
appears each time I open the project in VS2005, and if there may be some
caveats to be aware of while I maintain projects temporarily under both
VC6 and VS2005 (eventually porting them to VS2005). In a previous related
post, David W. advised me to use separate output directories for VC6 and
VS2005, but this question relates more specifically to this warning
message, and how VS2005 maintains the project (which is why I am asking
this question under a new thread).

Thanks much.
Do you open the .dsw file with VC2008 every time you open the project?
VC2008 will create a .sln project file, and you can open it instead of
.dsw.




.

Relevant Pages

  • ndis.lib linking problem.
    ... Searching libraries ... Searching C:\Program Files\Microsoft Visual Studio 8\SmartDevices ... asyncmac.obj: error LNK2019: unresolved external symbol ...
    (microsoft.public.windowsce.embedded.vc)
  • ndis.lib linking problem.
    ... Searching libraries ... Searching C:\Program Files\Microsoft Visual Studio 8\SmartDevices ... asyncmac.obj: error LNK2019: unresolved external symbol ...
    (microsoft.public.windowsce.app.development)
  • Re: afxtempl.h compiler warnings
    ... Studio 6 to Visual Studio 2005. ... 'new' no previous #pragma push_macro for this identifier ... in the afxtempl.h header file, and also seven occurrences of: ...
    (microsoft.public.vc.mfc)
  • Re: Compatibility issues between DX90b and VS2005
    ... 'PVOID64' c:\program files\microsoft visual studio ... Warning 6 warning C4819: The file contains a character that cannot be ...
    (microsoft.public.win32.programmer.directx.graphics)
  • Re: Compatibility issues between DX90b and VS2005
    ... 'PVOID64' c:\program files\microsoft visual studio ... Warning 6 warning C4819: The file contains a character that cannot be ...
    (microsoft.public.win32.programmer.directx.graphics)