Benefits of the Win32 API for .NET.

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.

  • What is the advantage that the Win32 API will still have over .NET in 3-5 years.
+3
source share
6 answers

Win32 - you can create your own tiny executables that simply reference what you want.

+7
source

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 Windows.

+3

Win32 API, . API- , - (PInvoke). .

+1

, . API Win32 , Windows . , ( ) C Win API, , ( ) Windows. , , .NET, - .

- Windows, , , , . , Win32 API - .NET( API ). Perhapse, , ... Managed ++, API C Win32. , API , API .NET, - , .

+1

.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.

0
source

Have you ever seen the MFC app? How about win32 in direct C? Pure pain and heartache..NET makes coding fun and easy.

-2
source

Source: https://habr.com/ru/post/1723053/


All Articles