Visual C++ CLR / Win32
So, I've been using Visual C# for a while but do not like how .NET Framework is required on computers to run the programs. It also seems bulky and slow. I took some C++ classes years ago, but we only made it as far as all the boring Console apps they made us do.
I want to start writing Win32 programs with a GUI in C++ but have ran into a concern. If I choose to do a Win32 Project, it looks like you have to design your GUI all through the code.
But in Visual Studio C++ 2008, it lets you create a CLR Windows Forms Application, and you use the C++ programming language. However, will CLR require that .NET Framework be installed as well? I think CLR uses .NET information, or something. But I'm not entirely sure, as I have not used C++ probably since before Microsoft had Visual Studio 2005. I don't like the whole .NET Framework dependency, even if it makes programming easier.
I want to start writing Win32 programs with a GUI in C++ but have ran into a concern. If I choose to do a Win32 Project, it looks like you have to design your GUI all through the code.
But in Visual Studio C++ 2008, it lets you create a CLR Windows Forms Application, and you use the C++ programming language. However, will CLR require that .NET Framework be installed as well? I think CLR uses .NET information, or something. But I'm not entirely sure, as I have not used C++ probably since before Microsoft had Visual Studio 2005. I don't like the whole .NET Framework dependency, even if it makes programming easier.
The GUI available as a library. In C#, the library is .NET and is bound at runtime.
The Microsoft way of getting a C++ GUI going is to use MFC. The binding is performed at compile time, so it's faster at runtime (even though the code is available as a runtime library).
They both have a learning curve and use different terms to mean the same thing. There's no such thing as a standard GUI.
The Microsoft way of getting a C++ GUI going is to use MFC. The binding is performed at compile time, so it's faster at runtime (even though the code is available as a runtime library).
They both have a learning curve and use different terms to mean the same thing. There's no such thing as a standard GUI.
The short answer is: yes, it will require the .NET framework.
When Visual Studio compiles the code into the executable, it really just compiles it into code that the .net framework can understand. Then, when the program runs, it calls the .NET framework to run the code.
If you select a win32 application, however, it does not require the .NET framework to run.
When Visual Studio compiles the code into the executable, it really just compiles it into code that the .net framework can understand. Then, when the program runs, it calls the .NET framework to run the code.
If you select a win32 application, however, it does not require the .NET framework to run.
> If I choose to do a Win32 Project, it looks like you have to design your GUI all through the code.
No, use the Dialog Editor
No, use the Dialog Editor
Thanks for your replies! Yeah, I definitely don't want to use the CLR if it requires .NET Framework. When I get home, I'll have to re-install the Professional Edition of Visual Studio 2008 to gain access to the MFC and/or Win 32 with Dialog Editor. I was just using the VS C++ 2008 Express Edition at work and noticed that MFC wasn't available in the Express version, nor was Resources, so I could not use the Dialog Editor.
Thanks!
Thanks!
Topic archived. No new replies allowed.