> I'm really not excited about the prospect of continuing to add new
> project files every year for each new version of Visual Studio. Isn't
> there any sort of backward-compatibility that allows the older files to
> work in newer Visual Studio releases?
Don't hold your breath - it might be there, but think about the upgrade
treadmill for a moment and you'll see why it's not in MS's interests to
support anything other than "sure, we can read the old project file and
upgrade it to the incompatible new version". That way, the developer
who has splurged on the new version shares unusable project files with
the rest of the team, who are pressured thereby into upgrading. Same as
the reason word processor file formats have to change at every release -
use network effects to turn your customers into stooges for your
marketing department.
Eddy.
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
