Help understanding .NET

[subnet_rx]

After studying the C++ language for some time, I want to create a GUI in Visual C++ 2003 .NET I'm not sure exactly what I am supposed to use. I can't find very many tutorials that work from a "Hello World" tutorial up. And I don't know if .NET is has native GUI API's or I'm supposed to use MFC (which I can't find an updated MFC book that's been written in the past 4 years).

Of the sites I have found it goes C++/MFC or C#/.NET. C++ can't use .NET? C++ still uses MFC? I'm dumbfounded.

Tutorials or just general info would be very helpful.

[bithub]

C++ can use .NET, but most people choose to stick with MFC (or the native windows API). As for an MFC book, the best is "Programming Windows with MFC" by Jeff Prosise. I've never used .NET so I can lead you to any good tutorials for that, but someone else here can probably oblige.

[naruto]

Microsoft seems to stop to update MFC but technical support is available. I think if you want to build normal business application program, C# is the best choice in Win32 platform.

Using C# to write a GUI "hello world" program is very easy just like VB. Drag a static control to the form to display the "hello world" information, or you can directly invoke MessageBox function to display the information.


"Programming Microsoft .NET" by Jeff Prosise is recommended to understand actual .NET programming skills. "Essential .NET" by Don Box and "Applied Microsoft .NET Framework Programming" by Jeffery Richter are the best two books for understanding the internal mechanism of .NET platform.

[Dante Shamest]

If you're going to use .NET, you'll have to make sure your target user has installed the .NET framework in his computer. It won't run without it.

If you use MFC, you have to distribute the necessary MFC DLLs along with your application.

If you use pure API, most of the time you just need to distribute the .exe itself.

[nvoigt]

With C++ you can do different things:

C++ Win32 Application

C++ MFC Application ( Framework including Window Classes )

Managed C++ ( .NET Framework including Window Classes )


C++ can use .NET. The reason most sites use C# as examples is that unmanaged C++ has one advantage to C#: it's faster. If you give up that advantage and use managed C++, you have all the drawbacks of C++ without the advantages, so it would be better to use C# from the start.

Managed C++ ( meaning C++.NET ) is usefull when interoparating with unmanaged C++ code or when the preprocessor and macros are extensivly used. If this is not the case, you are way better off using C#, or, if you need that extra bit of speed, normal C++ ( maybe with MFC support ).

[bithub]

"If you use MFC, you have to distribute the necessary MFC DLLs along with your application"
No you dont. Every single windows version since windows 3.11 has the MFC dll file included already.

[subnet_rx]

well, the reason I went with C++ is simple, Linux. I may use MFC now to create applications, but later, I would like keep myself open to being able to develop Linux or cross-platform applications also.

[BMJ]

The reason most sites use C# as examples is that unmanaged C++ has one advantage to C#: it's faster.

This is true most of the time.

Personally I find C# to be very straightforward and awesome for GUI applications, but sometimes MC++ is useful because I'm more familiar with C++ than C#.

Managed C++ and C# both use CLR and interops, they are both adequate for creating .NET applications.

Also, currently C# assemblies using v1.0 or 1.1 of the .NET framework are compiled completely into MSIL, whereby MC++ is compiled into a mixture of MSIL and x86. But .NET 2.0 will allow C# to compile assemblies as platform specific x86, IA64, or AMD64 (.NET 2.0 will provide 64-bit runtimes)

As .NET continues to evolve, MC++ will become less and less useful IMHO. (except for small interop functionality and any low-level data processing)



btw, C# isn't "anti-Linux"... in fact, technically C# is standardized and not platform-specific. See www.mono-project.com