| Author | Message | Time |
|---|---|---|
| ColT | What is better, Visual C++ or Visual C++.net? Also, why is it better and is there any difference in them for coding. Right know, I program in Visual C++ 6.0. | January 5, 2005, 12:36 AM |
| Myndfyr | If you're going with C(++), go with 6. .NET adds a lot of nice class library, but if you want to use it, you'll be dealing with a lot of __gc all the time. And __pin. It's ugly. [edit] Yes I'm silly. The 2002 and 2003 IDEs are significantly easier to use, and much cleaner, if you're doing just C++. If you use 2002/2003 and use .NET, that's when it gets ugly. :) [/edit] | January 5, 2005, 3:00 AM |
| Mephisto | VC7 (.NET 2003) is fine for C++, but it makes little difference if you're using it just for C++ really. | January 5, 2005, 4:01 AM |
| K | Actually, either way go with .NET (2003), if you're just talking about the IDE (Keep in mind there is no such language as "Visual C++" unless you mean MFC -- it's all just C++) It's just an IDE. The .net 2k3 compiler is much more standards-compliant than 6.0. | January 5, 2005, 5:02 PM |
| ColT | Ok, lol. Well thanks. | January 5, 2005, 11:57 PM |
| Zakath | Yes, get .NET 2003 if you can. Most user-friendly IDE, most intelligent compiler (in general). | January 7, 2005, 7:57 PM |
| ColT | Is there much difference in .NET 2003, and C++ 6.0? | January 8, 2005, 1:17 AM |
| Barumonk | In .NET, you can mix normal C++ code and .NET code in the same application. If your not trying for speed then its great. In .NET you don't need to worry about releasing objects as much as in normal C++, but it does still matter. Most of the time you will find yourself implementing the IDisposable interface on managed reference types to eliminate 3rd generation+ GC objects that aren't being used by the application anymore. In certian situations, not worrying about allocating and disposing the managed objects and letting the GC handle them can speed up your application beyond that of a normal C++ application, but it generally requires some type of strategy (dispose pattern). If you really get lazy, when someone complains that there is no linux or mac versions, you can direct them towards the Mono implementation of the framework, which requires no extra programming on your part. The .NET Portable framework is also in the works, but Mono is farther ahead at the moment. Thats all I can think of right now. ^^ | January 16, 2005, 1:43 AM |