What are the limitations of Loose XAML?

Question

I experimented with WPF and provided strict XAML markup in a web browser, also known as Loose XAML (explained here and here ).

It seems to me that this is useful for displaying static content. However, it is also possible to associate with an XML data provider.

Free XAML files are not compiled with the application, which creates the following restrictions:

• They do not allow external assemblies
• Without using classes, code (or any C #)
• No two way data binding

What additional restrictions exist?

• I did not find a way to bind data to the database provider (SQL Server)
• Is the .NET Framework required on the client machine to display XAML in the browser?
• Can search engines poll Loose XAML for proper page ranking?

EDIT: I tried to associate an XML data provider with a web service (using this simple example) and was not successful. These results lead me to further research when I discovered that this is not supported: "XMLDataProvider is designed to be read-only (in other words, it does not make it possible to make changes), and it is not able to process XML data that may come from other sources (e.g. database record, web service message, etc.). -Matthew MacDonald, Pro WPF

Answer 1

AFAIK XAML. , SQL- .

. -, XmlDataProvider. , ...

: btw, Sandboxed, , XBAP XAML, , , , - .

Answer 2

XAML IE , , 3.0. , ".NET CLR 3.0" .

, , XAML - .

Answer 3

Dynamic Language Runtime (DLR) XAML. , , Loose XAML , , , Python/Ruby/JScript, , SQL-.

blog, , .

- .

So, also answer the question, there are many limitations of Loose XAML out of the box (for example, the inability to route events to an event handler), but they can be overcome with a little work.

I used XAML / WPF for desktop applications only. Hope someone else jumps in to answer your browser related questions.

I have a library that I use in commercial work for DLR hosting and embedding DLR scripts in XAML, which I mean to turn into a supported product. If this interests you, be sure to let me know.