http://blogs.msdn.com/lifeontitan/archive/2004/02/04/67664.aspxLet's create a new Window in Win32: HWND hwndMain = CreateWindowEx( 0, "MainWClass", "Main Window", WS_OVERLAPPEDWINDOW | WS_HSCROLL | WS_VSCROLL, CW_USEDEFAULT, CW_USEDEFAULT, CW_USEDEFAULT, CW_USEDEFAULT, (HWND)NULL, (HMENU)NULL, hInstance, NULL );en-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/lifeontitan/archive/2004/02/04/67664.aspx#67719Thu, 05 Feb 2004 05:03:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:67719Jerry PiskThe code does not produce the same result (Window class is different). Of course it looks simpler if you exclude things that are difficult to do. And once you start creating windows that do not use all defaults Win32 is going to start a lot simpler (a single command as opposed to a lot of commands in .Net).http://blogs.msdn.com/lifeontitan/archive/2004/02/04/67664.aspx#67728Thu, 05 Feb 2004 05:29:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:67728CharlesYou are technically correct of course... CreateWindowEx returns a handle to the created window. The .NET example returns a Window object, which, yes, is not an HWND. The point is that is takes very little code to create a Window in the new Windows API. The pattern is much more elegant. <br> <br>Note that each of the above code fragments creates and shows a window with default settings. You are going to be surprised how easy we are making Windows programming in Longhorn. <br> <br>Charleshttp://blogs.msdn.com/lifeontitan/archive/2004/02/04/67664.aspx#67991Thu, 05 Feb 2004 16:56:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:67991Michael Malinak.NET and the WinFX always make things shorter if you want to create a default object. The issue is when you want to tweak the fine settings. <br> <br>Yes Win32 is much more clumsy and nasty to look at. But it does make it easy to get rid of WS_HSCROLL and WS_VSCROLL. I must say that when creating _real_ applications I end up customizing windows much more often than using the default settings. <br> <br>Yes it's nasty, but it is powerful. It also didn't help that some (alot) functionality that is available in Win32 isn't accessible from .NET without using Interop.http://blogs.msdn.com/lifeontitan/archive/2004/02/04/67664.aspx#68157Thu, 05 Feb 2004 21:59:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:68157CharlesMichael, one of our goals as we proceed with with the evolution of the .NET Framework is to limit the amount of pInvokes required by you while writing a managed Windows application. Of course, this means that the Framework will take care of interoping with COM internally. We are many years a away from a fully managed operating system. Do you have specific feedback regarding your experience with WinFX and Longhorn? What do you think? Do you like what we are doing in Longhorn? I'd love to get your feedback on our new Windows technologies as presented in the PDC build of Longhorn. <br> <br>Charleshttp://blogs.msdn.com/lifeontitan/archive/2004/02/04/67664.aspx#6569526Wed, 28 Nov 2007 08:54:17 GMT91d46819-8472-40ad-a661-2c78acb4018c:6569526Windows and .NET: We're making it simpler<p>PingBack from <a rel="nofollow" target="_new" href="http://feeds.maxblog.eu/item_505685.html">http://feeds.maxblog.eu/item_505685.html</a></p>