mrkcoconnell wrote: > Hi, > > I have a number of legacy applications written in VC6. I tried (for an > experiment) to convert to VS2003 and had nothing but problems. VC2003 on to > later editions are not good at backward compatibility. This is largely due > to switching from a VC runtime to a dot-net runtime. These are very > different run-time environments. There is a project in VS2003 that used MFCs > but the whole run-time is meant to use dot-net. I don't mean to suggest this > cannot be done, only that there will be a good deal of work to do in the > process. > > Here is the real question...is there a good reason for converting? You will > undoubtedly have a lot of work and for what. What advantage will you have > when you are finished? > > Kevin
Exactly why VC6 is still in heavy use. The really old, crusty, non-Standards compliant code won't port cleanly over to newer versions of VS. I've heard reports that such code turns into unreadable mush. If this happens to you, it could just be an indicator that the application needs to be re-written. A good time to do a complete reworking of an application to clear the cobwebs and get a fresh design on the table. -- Thomas Hruska CubicleSoft President Ph: 517-803-4197 *NEW* MyTaskFocus 1.1 Get on task. Stay on task. http://www.CubicleSoft.com/MyTaskFocus/
