Worrow Posted December 7, 2007 Posted December 7, 2007 Just start trying XAML. Put a button and a textbox in it and built the application. The size of file seems the same as the WinForm one, but when I ran the application it took like 20+Mb instead of 8+Mb(for the WinForm, which I consider is huge already). Why the XAML made form takes so much memory? Doesn't XAML get transform into CLR which should be the same as the WinForm? I am surely missing something here:confused: Quote
Administrators PlausiblyDamp Posted January 24, 2008 Administrators Posted January 24, 2008 A bit late answering this one I know but... XAML applications are fundamentally different to a normal window application, even though the code itself is compiled down to MSIL the actual front end isn't built using standard windows controls. WPF applications have their own windowing system based around DirectX and it is probably this extra overhead that is accounting for some of the differerences in memory usage. WPF really is designed for newer systems with plenty of resources and cpu / graphics power as opposed to older and lower specced machines. Quote Posting Guidelines FAQ Post Formatting Intellectuals solve problems; geniuses prevent them. -- Albert Einstein
Worrow Posted February 6, 2008 Author Posted February 6, 2008 Which means XAML is supposed to build more fancy UI? That clear things up, thanks!:) Quote
Administrators PlausiblyDamp Posted February 7, 2008 Administrators Posted February 7, 2008 XAML can do a lot of fancy UI stuff, including the separation of layout from code for a lot of the day to day things. As an example the author of this book has a sample RSS reader done entirely in XAML and no procedural code used at all. Quote Posting Guidelines FAQ Post Formatting Intellectuals solve problems; geniuses prevent them. -- Albert Einstein
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.