Hello, I have posted an article on The Code Project:
http://www.codeproject.com/gen/design/xaml.asp That discusses how to write .NET assemblies that are "friendly" to XAML parsers like MyXaml (www.myxaml.com). Comments are welcome! Basically, the six golden rules are: 1. not too many namespaces 2. public, default constructors 3. properties for everything you want to expose to the outside world 4. type converters when .NET can't handle the conversion itself 5. collections derived from IList and instantiated at construction time if read-only 6. implement events for UI actions and property setters, where appropriate The article has a very brief overview of XAML and discusses these 6 rules in a little more detail. Enjoy, Marc ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ xul-announce mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xul-announce
