Changes from VS 6 to VS NET 2003

Using the same reasoning, why Java, why C++, why C, why Macros in assembler, why not link the programs yourself, the linker adds 'bloat' too ?

java is total difference than .net ... i know your point of view but also c++ and C is also totally difference,.. all of them run very stable and fast like old school ASM programing rulez... for example compile your Visual Basic 6 or C++ application like classic method.... now transform it to .NET ... don't tell me bull_shit it will be the same... and i know what i'm talking here.. i'm not kidding/playing kids games here. i'm not a programmer but i know what i wrote.
i respect your desicion and likes.. i know you like .NET but i made an opinion like anyone else .. for me .NET suc_ks ... you should respect my point of view as well.

I'm not defending .NET against any other technology, I'm just stating that you have no idea what you are talking about. I'm not argueing on whether you can like the language or not; I'm pointing you the reasons for the existance of this language and why it is used.

You don't compare languages strictly by the size & speed of the the executables they produce. If that's how languages were determined as good ("assembly rulez") or bad ("30 mb crap of libraries"), we would all be programming in assembly, which clearly is not the case.

Who cares about C++ and VB... managed code is all about C#. You missed the point.

Hello,

I agree with Arc, if you start a new project you'll see that only C++ has 5 subgroups (NET, MFC, Win32), so C++ will not force you to use .NET.

If you want to build Win32 apps but not using managed code, framework is not that good compared with the managed code.

Micro$soft is really pushing NET. Yesterday I installed Win2003 server and it comes with NET framework. But one thing is I do not understand why do they have two from designers in C++, one for managed code and one for unmanaged. They could come up with one designer. It seems that they won't more money from their customers.

Anyway, if you want to still producee Win32 app my advice to you is stick with the VS 6. VS.NET will not give you any real advantages when it comes to Win32 apps. VS.NET IDE is better, but VS 6.0 still rocks.

Regards,
asmith

Originally Posted by AgentSmith

VS.NET will not give you any real advantages when it comes to Win32 apps. VS.NET IDE is better, but VS 6.0 still rocks.

I would argue with this. The C++ language support is definitely a point it is worth changing for. I don't treat VS6 a C++ compiler, but for mainly C projects it is almost as good as VS.NET.

[ArC]

But one thing is I do not understand why do they have two from designers in C++, one for managed code and one for unmanaged. They could come up with one designer. It seems that they won't more money from their customers.

Hm I never really used managed code but I assume it's because of the dialog elements. .NET provides additional dialog elements and properties (such as the background color of a dialog; the form/dialog editor for native apps does not provide this functionality).