This is a paraphrase of an earlier question that has hit the community badly. Fairly, this might be too logical.
Since I'm really interested in what people think about it here, I hope this more specific question will be accepted.
Win32 - you can create your own tiny executables that simply reference what you want.
Most agree that Win32 has many flaws. Here are a few advantages that, in my opinion, do not outweigh the disadvantages:
Win32 Windows, .net.
Win32 Windows.
Win32 API, . API- , - (PInvoke). .
, . API Win32 , Windows . , ( ) C Win API, , ( ) Windows. , , .NET, - .
- Windows, , , , . , Win32 API - .NET( API ). Perhapse, , ... Managed ++, API C Win32. , API , API .NET, - , .
.Net still does not give you direct access to the kernel’s native API functions and probably never will, since one of its intentions is to abstract you from the OS to make your code more platform independent.
Have you ever seen the MFC app? How about win32 in direct C? Pure pain and heartache..NET makes coding fun and easy.
Source: https://habr.com/ru/post/1723053/More articles:What IDE allows me to view diff as highlight on my code? - diffDoes VBA keep a cache of past code changes? - vbahtaccess rewrite causes a 500 error instead of 404 - .htaccessПолучить контекст из UIImageView - iphoneIs there an ORM scheme for Cocoa or a structure that accomplishes a similar goal using a different technique? - cocoaHow to determine which input bus is active when AUEffectBase :: Render is called? - c ++DataGridView / Enter Key? - datagridviewphp session.use_trans_sid - phpUINT64 casting for swimming? - c ++clojure проблема с rmi classpath - classpathAll Articles