Linked by Thom Holwerda on Thu 20th Dec 2007 10:13 UTC, submitted by meianoite
Thread beginning with comment 292794
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Not good enough...
by memson on Sun 23rd Dec 2007 15:32
in reply to "RE[4]: Not good enough..."
No, the point is more to do with uncontrollable forces. ASP.Net 1.0 and 2.0, to give an example, are runtime compatible, but until re-added web projects, as per VS.Net 2003, there was a forced upgrade that implied a whole new extensive full regression test. Fuller than if they had left well alone.
Any time you change runtimes - and to use 3.5 features, that is implied, the costs for all product releases ramp up. Releasing a product without fully testing is exactly the type of foolish behaviour that ruins customer relationships and loses sales.






Member since:
2005-07-07
As with Java, .NET is able to support multiple runtime environments on the same machine so the whole issue of 'upgrading' to .NET 3 or Java 6 is moot from an end-user perspective.
Of course I agree with you completely though - it all depends on the customers. If your market research or feedback from customers leads you to believe that they are not willing, for whatever reason, to use the latest runtime environment then of course that's a valid reason not to upgrade your development environment.
In the end-user market you are very unlikely to come across that type of customer though.