"I have a mind like a steel... uh... thingy." Patrick Logan's weblog.

Search This Blog

Loading...

Tuesday, May 25, 2004

XAML as a document format --- might work

Update: Wes writes in the comments:

Microsoft has foreseen versioning issues with XAML. The XAML parser does allow custom mappings between names of elements and attributes to their corresponding .NET types and properties, so that is not really an issue.
This would seem to allow a developer to map a version 1.0 document's class names and properties to a version 2.0 implementation's classes and properties. Good news. The original concern is still there: that XAML embeds the implementation at all is a stronger bind to dotnet than XML generally should have. But that's a business decision, not a technical one. At least within versioning dotnet applications, using XAML as a "document" should have an upgrade path for document versions.

Original post:

I am not sure about the wisdom of using XAML as a "document" format. As I wondered previously, wouldn't this embed in a "document" essentially the classes, instances, methods, and properties of the *implementation*?

Can someone explain how this isn't so? Or explain why this is a good thing for a document format?

Surely implementations should be able to change without having to upgrade their documents!

6 comments:

Wes said...

XAML contains a reference via the directive to the assembly containing the controls that the document refers to, so the code need not be in the document.

That said, it is conceivable that Longhorn will allow the document to contain code; however, any code would be running in a sandbox, and any attempt to perform an unpermitted operation would result in a Code Access Security exception. Longhorn security does take into account the source of the document, so I am guessing it may be possible for the document to run unrestricted code. (Wesner Moise)

Patrick Logan said...

My concern is not about code and security. Rather it is about design and change. If you embed class names and properties, those objects become resistent to change, even if you'd like them to.

Wes said...

Microsoft has foreseen versioning issues with XAML. The XAML parser does allow custom mappings between names of elements and attributes to their corresponding .NET types and properties, so that is not really an issue.

Alex said...

Completely agree. Our current project has 7 levels of metadata clearly separated (UI, BLL, DAL and intermediary. I wll write about this framework someday). We're using XSL to create C# classes and we like this approach. If tomorrow a client should tell us to use Java (or whatever) all we need to is define onother rules to roll up the implementation!

cash at home said...

Hello There, My name is Donald you have a great blog here! I'm definitely going to bookmark you! I have a make money with a pick up truck
site. It pretty much covers make money with a pick up truck
related stuff.

Come and check it out if you get time :-)

TS said...

Nice Blog!!!   I thought I'd tell you about a site that will let give you places where
you can make extra cash! I made over $800 last month. Not bad for not doing much. Just put in your
zip code and up will pop up a list of places that are available. I live in a small area and found quite
a few. MAKE MONEY NOW

Blog Archive

About Me

Portland, Oregon, United States
I'm usually writing from my favorite location on the planet, the pacific northwest of the u.s. I write for myself only and unless otherwise specified my posts here should not be taken as representing an official position of my employer. Contact me at my gee mail account, username patrickdlogan.