winapi - How do I decide whether to use ATL, MFC, Win32 or CLR for a new C++ project? -
I'm just starting my first C ++ project I'm using. This is a single-form Windows application that accesses some databases and initiates a WebSphere MQ transaction. I basically understand the difference between ATL, MFC, Win Win32 (I'm actually a little blurred on one) and CLR, but I have to face the loss of how I should choose.
Is one or more of these for backward-compatibility?
Any suggestion is appreciated.
Edit: I have chosen C ++ for this project because of my reasons. I will go into the post, which is not complete technical, therefore, Assuming C ++ is the only / best option, which should I choose?
It depends on your needs.
Using CLR will provide you with the most meaningful libraries (the entire .NET framework) at the cost of restricting its executable to the NBT framework. Can be installed at runtime, as well as you can limit the Windows platform (though, all 4 listed technologies are only Windows, hence the platform limit is the least problem).
However, CLR is required to use the C ++ / CLI extension in the C ++ language, so in a nutshell you will need to learn some additional language features to use it. Doing this gives you access to many "extra", such as .NET libraries, complete garbage collection, etc.
ATL & amp; To decide between the MFC is somewhat complicated, I will refer you to making a decision between them. The good thing about ATL / MFC is that you do not need the .NET framework, only VC / MFC runtime for deployment is to be established.
The use of Win32 directly offers the lowest performance, with the least dependencies, but more work is for writing. You have the least amount of support libraries, so you are writing more code Are there.
Comments
Post a Comment