|
You underestimate the power of the dark side of the code: legacy. 
We have ported most of our applications to 2008, but a couple of the bigger one would require more work that is worth (or that we can afford) at the moment.
After all, I hear there are still some COBOL applications running around somewhere. In comparison, VC6 is still brand new! 
|
|
|
|
|
Remember, there are many unlucky souls that maintain lagecy code. 
|
|
|
|
|
but you can build the same code using vs2010 
d{^__^}b - it's time to fly
|
|
|
|
|
Only if that were true. Each new compiler broke backward compatibility a bit with the improved adherence to the standard. So moving to a new compiler may be a bit of work. Years ago I moved 500K lines of my code + codeproject code used in my applications from VC6 to VS2003. That took over 3 months of my time. The biggest problems were templates and MFC and making changes in the codeproject code. If I remember correctly there were 1 to 3 thousand individual changes needed. This code still sits at VS2003.
John
modified on Thursday, June 3, 2010 8:31 AM
|
|
|
|
|
|
That is easier said than done. I wish upgrading was that simple.
|
|
|
|
|
yes i still use it sometimes on old projects needing updates or bug corrections
|
|
|
|
|
Most of the code I write is hardware related. Have you ever tried VS2010 on a 486 with a 500MB HD. VS6 for the Old? VS2010 for anything new. If there were limitless time and money I sure most of us would plump for the new shinny things "Ipad anyone", but most of the time its as cheep and as quick as possible
Why is it when you are busy everyone whats it yesterday, But when your not no-one has any work for you?
|
|
|
|
|
VB6 refuses to give up the ghost.
|
|
|
|
|
d{^__^}b - it's time to fly
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
