Upgrading VC6
-
Hi all, I want to upgrade from VC6 to VS 2003 or 2005, but need to be able to keep my existing projects in VC6 until they are fully working in the new compiler. Are there any issues with installing both systems together or are they best kept well apart?
-
Hi all, I want to upgrade from VC6 to VS 2003 or 2005, but need to be able to keep my existing projects in VC6 until they are fully working in the new compiler. Are there any issues with installing both systems together or are they best kept well apart?
-
Hi all, I want to upgrade from VC6 to VS 2003 or 2005, but need to be able to keep my existing projects in VC6 until they are fully working in the new compiler. Are there any issues with installing both systems together or are they best kept well apart?
I am using VC6 and VS2001 together, no problems. Except that, if you try to run your VC6 code on a later system, you will be told that it needs to be altered first. If you allow this to happen and open your old programs on you new IDE, I don't know of any way to go back. So until you choose to move your code over, it is certainly best to keep the projects apart. I had a fairly large project on VC6 and decided to use VS2001 on it. This was fine for a long time, but a week ago I finally ran into some problem that I could not resolve, and decided that the time had come to properly update my project. So I made sure I had an extra backup, renamed the old folder, created a new project in VS2001, and transferred all the source files over. This tooke a morning, what with having to change a lot of include paths due to VS2001 using s different layout from VC6 for its files. But it was certainly worth it in the end to move to a newer system. Cleared out a lot of junk files in the process. But I still use VC6. For one thing, there is inforamtion in its help system that you will not find in VS2001 and, I assume, in all later versions. And from time to time I come across code written for VC6 which I would not want modified. I would upgrade to VS2005 if I could find a supplier. Whether I would then still use VS2001, I don't know. Buying it was a bit of a mistake, being a new IDE at the time. More mature code tends to have bugs / deficiencies that are less glaring. Shraddhan
-
I am using VC6 and VS2001 together, no problems. Except that, if you try to run your VC6 code on a later system, you will be told that it needs to be altered first. If you allow this to happen and open your old programs on you new IDE, I don't know of any way to go back. So until you choose to move your code over, it is certainly best to keep the projects apart. I had a fairly large project on VC6 and decided to use VS2001 on it. This was fine for a long time, but a week ago I finally ran into some problem that I could not resolve, and decided that the time had come to properly update my project. So I made sure I had an extra backup, renamed the old folder, created a new project in VS2001, and transferred all the source files over. This tooke a morning, what with having to change a lot of include paths due to VS2001 using s different layout from VC6 for its files. But it was certainly worth it in the end to move to a newer system. Cleared out a lot of junk files in the process. But I still use VC6. For one thing, there is inforamtion in its help system that you will not find in VS2001 and, I assume, in all later versions. And from time to time I come across code written for VC6 which I would not want modified. I would upgrade to VS2005 if I could find a supplier. Whether I would then still use VS2001, I don't know. Buying it was a bit of a mistake, being a new IDE at the time. More mature code tends to have bugs / deficiencies that are less glaring. Shraddhan
Shraddhan wrote:
I am using VC6 and VS2001 together, no problems. Except that, if you try to run your VC6 code on a later system, you will be told that it needs to be altered first. If you allow this to happen and open your old programs on you new IDE, I don't know of any way to go back.
But you can - with a slight overhead of work, maintain the old as well as the new Project files and Solutions. This way, your codebase can be used from both IDEs. The work-overhead comes from activly *not* using new features of the VC7.1-compiler, keeping the VC6.0 comments for the class wizard intact, and from maintainig two sets of incompatible compiler output directories.
"We trained hard, but it seemed that every time we were beginning to form up into teams we would be reorganised. I was to learn later in life that we tend to meet any new situation by reorganising: and a wonderful method it can be for creating the illusion of progress, while producing confusion, inefficiency and demoralisation." -- Caius Petronius, Roman Consul, 66 A.D.
-
Shraddhan wrote:
I am using VC6 and VS2001 together, no problems. Except that, if you try to run your VC6 code on a later system, you will be told that it needs to be altered first. If you allow this to happen and open your old programs on you new IDE, I don't know of any way to go back.
But you can - with a slight overhead of work, maintain the old as well as the new Project files and Solutions. This way, your codebase can be used from both IDEs. The work-overhead comes from activly *not* using new features of the VC7.1-compiler, keeping the VC6.0 comments for the class wizard intact, and from maintainig two sets of incompatible compiler output directories.
"We trained hard, but it seemed that every time we were beginning to form up into teams we would be reorganised. I was to learn later in life that we tend to meet any new situation by reorganising: and a wonderful method it can be for creating the illusion of progress, while producing confusion, inefficiency and demoralisation." -- Caius Petronius, Roman Consul, 66 A.D.
jhwurmbach wrote:
But you can - with a slight overhead of work, maintain the old as well as the new Project files and Solutions
Well, I suppose that this is a possibility. But unless there is a good reason to be able to use both IDEs on the one solution / project, I prefer to make a clean change over. (And what if I had both IDEs open at the same time on the same project? Chaos...) Shraddhan