"Ajay" <ajayka...@yahoo.com> wrote in message
news:1779301b-019e-4150-82c9-c8594bb144b7@w1g2000prk.googlegroups.com...
VC6, for all its strengths, had a poor debugger even prior to
Vista. At least its remote debugging was poor. But I believe it
is possible to use VC6 on Vista to build and develop the app,
then debug it using VC2005 or VC2008.
Sounds like someone really wants to avoid the new IDEs :-). ..
Looks like AnthonyW has been able to use it on Vista.
Just a week ago I was using the AMSEdit series of masked edit
controls from CodeProject which had not been updated from VC6.
They would not build with VC2005 or 2008. The compiler errors were
not easy to figure out how to change the source code; in fact
several people had tried and given up, due to the, errr....
uncommon multiple inheritance the class was using. So I was faced
with either using VC6 or struggling through the conversion. It
took me a half a day but I finally converted (and posted the
changes to CodeProject). But I can easily see how converting to VC
2005/2008 is non-trivial.
convert existing C# projects from VS2005 to VS2008 etc. We can take
baby steps and target the older .Net version if we want. VC++