Is Visual C++ 2005 a lot better than VC++ 2003 ?

[Defenestration]

For standard C++ programming and also WTL programming, is VC++ 2005 a lot better than 2003 ? Is the IDE a lot better in 2005 ? Is it worth upgrading from 2003 to 2005 ?

[rahulmballal]

I dont know about you but I find the new Visual C++ to be a lot cleaner than the previous VC++. The simple reason being the concept of partial classes where the code wizard writes code in a separate file but for the same class. So there is 1 file with your implementation and one with the code gen. There is no need to find you way through the code and make changes or insert code as in 2003 at times. It does not support .net 1.1 framework but does it for .net 2.0. The GUI that u can build is very Office 2003 like...so it looks updated cheers Rahul

[Rage]

Yes, it is worth upgrading. Someone blamed for my nickname to be destructive, I wonder what he would have said about yours ;) ~RaGE();

[topus]

I ave tryed 2003 and 2005 but after some disaventure (serialization of CObject defined in extension DLL see IMPLEMENT_SERIAL_EXTDLL ecc.. distributing executables ecc..) I use VC++ 6!

[Rajesh R Subramanian]

The upgrade is worth doing.

topus wrote:

I use VC++ 6!

But yes, VC++ 6 still ROCKS! Regards, Rajesh R. Subramanian You have an apple and me too. We exchange those and We have an apple each. You have an idea and me too. We exchange those and We have two ideas each.

[toxcct]

:laugh:;P not so bad, but quite old nowaday :-D i still use it, but only when i maintain a project a create under VC++6 that i don't want to port to VC++7.1. now, when i create new projects, i use VC++2003 (i don't have VS2005 except a beta2), and i find it pretty cool compared to VC6 (which keep me nostalgic :rolleyes: )

---

TOXCCT >>> GEII power
[toxcct][VisualCalc 2.20][VisualCalc 3.0]

[Cedric Moonen]

topus wrote:

I use VC++ 6!

Yep, still a good IDE but there are some minor bugs with the compiler. If I remember correctly (not sure anymore), you will have compile errors when you have a class with a private destructor and a public function that auto-deletes the object (something like): void MyClass::Destroy() { delete this; } The compiler will tell you that the class cannot access the destructor as it is private. There were also some minor bugs with the STL I think but I cannot remember anymore which ones.

[Lost User]

FWIW, I posted a thread on Visual Studio 2005 in The Lounge yesterday: http://www.codeproject.com/lounge.asp?msg=1332018#xx1332018xx[^]