By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,469 Members | 1,037 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,469 IT Pros & Developers. It's quick & easy.

VS project files backward compatibility

P: n/a
Hello, All!

Installed VS 2005... What is annoying is that project files are not backward
compatible.

For instance, EVC4 vcp files are backward compatible with EVC3 and can be
used simultaneously (moreover I could run EVC3 and EVC4 with the same
workspace at the same time).

vcproj files are in xml, why not to allocate separate node to store
configurations for studio 2005 and leaving 7.1 (aka 8.0 format)
configurations from 2003 in their sandbox, but sharing project's files list
and folders?

Best regards, Vyacheslav Lanovets
Jul 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Not only is it annoying, it is also profitable for MicroSoft.

I don't know about everybody else, but I don't have the $$$ to keep buying
into TheNextBigThing. Especially when it isn't that much different than the
TheLastBigThing.

Bob Lehmann

"Vyacheslav Lanovets" <xentrax_umail.ru> wrote in message
news:OT*************@TK2MSFTNGP10.phx.gbl...
Hello, All!

Installed VS 2005... What is annoying is that project files are not backward compatible.

For instance, EVC4 vcp files are backward compatible with EVC3 and can be
used simultaneously (moreover I could run EVC3 and EVC4 with the same
workspace at the same time).

vcproj files are in xml, why not to allocate separate node to store
configurations for studio 2005 and leaving 7.1 (aka 8.0 format)
configurations from 2003 in their sandbox, but sharing project's files list and folders?

Best regards, Vyacheslav Lanovets

Jul 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.