[quoted text, click to view]
#ifdef the inclusion of (for example) "iostream.h" or "iostream" based on
the compiler version because I want to ensure backward compatibility.
[quoted text, click to view]
I have a question and a suggestion...
Question: As <iostream> (without the .h) is supported in VS 6 as well as
VS.NET 2003 (which no longer supports iostream.h). Why do you need to do
this?
Suggestion: If you don't find what you need here, posting your question in:

microsoft.public.dotnet.languages.vc

will probably get you more feedback faster, as your question is C++
specific.

--
Peter [MVP Visual Developer]
Jack of all trades, master of none.

Hi Peter,

[quoted text, click to view]

_MSC_VER, for example it would be 1300 for Visual C++ .NET


Thanks!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

Hi,
thank you for your answers! My problem is that lot of developers in my company are still using VS 6.0 and others use VS.NET 2003. I wanted to share the same code base.
One good thing is that solution files (.sln) could live together with old .dsw files so I don't have to generate different projects, Simply I'll open .sln files in VS.NET2003 and .dsw in VS 6.0 (I hope that the same will apply to Whidbey).
Concerning the new header files (iostream, fstream) I chose to migrate to the new ones. For the otherissues I will use a preprocess macro for i.e.:

#if (_MSC_VER<1300)
#include <onlyforVS60.h>
#endif // (_MSC_VER<1300)

PS:
Sorry if this thread would fit better in "VC++" newsgroups..

Regards,
Diego


[quoted text, click to view]