I was wondering until when will you guys keep on supporting VStudio6 with the newest versions of VAX?
I was wondering if sometimes you guys makes compromises based on the fact that an 'older' ( either VS6 or VS2003 ) do not support that specific features/pre-requisits you guys want to implement, so you just drop the new feature all together?
How much of a factor is maintining compatibility with backward versions plays a role in new designs?
We don't believe we have ever forgone a feature because we wouldn't have been able to make it work in VC 6.0. Numerous other things drive our decisions about features -- primarily what we believe to offer the most benefit to our customers (and is reasonably possible to develop and maintain within a $129 product.)
Features in newer IDEs, i.e. in VS.NET but not in VC 6.0, don't get added to our product. (We assume VC 6.0 users will migrate at some point.) The exceptions are features we add to an IDE prior to MS announcing it for a newer IDE.
on a related note a lot of people here who do pure C++ development say that VC6 is by far the best IDE. certainly Microsoft have not done much to improve the editing experience for C++ programmers in the newer IDE's. just look at the improvements they have made for C# in VS2005 *sigh*
Backward compatibility hindering further devlps?
Posted - Mar 20 2006 : 8:25:58 PM
