What is the difference between .net and win32

So there is no reason to wrap all the Win32 API. Managed code frees programmer from memory usage optimization, safety, threads pooling and so on. For example fast performance network server programming, Firmware integration is not a best filed for. NET application. NET, C for example. It is not so simple like import Win32 API, but it is possible, even without automation.

From another hand,. NET is the main stream of Microsoft and they see Windows future in it. So, by definition they have no reason to expose any additional functions in Win32 API I am not talking about under carpet and undocumented calling and, of coarse, in future. Learn More. Ask a question. Quick access. Search related threads. This compensation may impact how and where products appear on this site including, for example, the order in which they appear.

TechnologyAdvice does not include all companies or all types of products available in the marketplace. Remember Me? Advertiser Disclosure. Advanced Search. Results 1 to 2 of 2. Results 1 to 5 of 5. May 7th, , PM 1. Join Date Jan Posts If you know the other ones please post a comment And Which one is the best out of all of them, not just the open ones and for what conditions?

I've been google-ing for like 3 hours now. Any thoughts are helpful. May 9th, , AM 2. Join Date Mar Posts 2, Actually there is Win32 for Linux. With Virtualization and products like VMWare and Xen, however it is possible to get away from needing portability all the time.

I think wxwidgets are great because they are portable. QT is portable too and people are always singing its praises. Sign up. Email Address. Careers Careers. Learn about game development. Follow Us. Chat in the GameDev. Back to For Beginners. For Beginners.

Started by muimui August 08, AM. Cancel Save. HAM MFC is basicly a library of OO wrapper classes that wrap the Win32 api, and provide objects for the basic window components windows, buttons, checkboxes etc..