.net - XAML - What's the point of (typing) it? -


I am currently looking into learning WPF and Silverlight. So far, I am developing in Delphi and C # (Winform). Looking at some books about WPF and seeing some introductory video online, I am seeing this XAM thing is far behind in terms of efficiency and applicability (for the developer). Specifically in online video, people are happily typing XAML code to create forms and controls, which I thought was a technique that was largely obsolete by the appearance of visual form designers. When using the first form designer, why do I want to write a text presentation in XAM or a button or grid? To choose from a dropdown list in an asset or inspector, when color comes quickly, why type the name of color or font? Is the real-world application GUI actually developed by typing XAML?

I'm sure I'm missing something here, though I do not know ... ...

I write all my XAML manually because I have not been able to blend so far. But some other developers work with Love using Blend and it's great to set things like gridants.

I recommend that you download Blend testing and give it a try, it really works well with Visual Studio and saves you a lot of time if you learn how to do it. is.


Comments