Because of the name of the relationship, WPF and wpf/e have always been considered to be something like that . In fact, boththe part that renders the UI uses the common language XAML Outside,There's a big difference in nature.. Even, XAML has different meanings for WPF and Silverlight, and it cannot be considered a "common language " between the two.
XAML , for WPF , is a kind of . NET programming language instead of using XML to describe it . Other words, XAML is used inOn WPF, like a different programming language. WithC #, VB, IronPython similar. SoThe XAML can do, C #, VB can do the same. But in turn, C #, VB can do, XAML does not necessarily doBecauseXAML is designed to work with development tools, a specially designed language.,itself has its limitations , so still have to cooperate with the formal programming language , in order to complete a really useful program . But with the currentThe capabilities of XAML, not byC #, VB to do the usual simpleFlash can do that, it should be no problem.. therefore, application = author of Code + markupPetzold will write the structure of the book first toC # to writeWPF program xaml. to avoid misunderstanding  WPF = XAML. XAML can also be used on the wf wpf. if xaml is used, it is considered Span lang= "en" >wpf all ! however ,xaml to Silverlight svg. XAML is used to describe the structure of the frame tree javascript to operate the ui tree . so lang= >silverlight "en" for tag. like firefox JavaScript to operate svg described in the picture
[goto] WPF and Silverlight relationships