EID and Standalone XAML
There is the potential for utilizing XAML functionality as an extension to the MacroView product line. As such I’ve been experimenting with various XAML tools including Microsoft Expression Interactive Designer. The direction for XAML use as part of MacroView is likely to be more oriented towards standalone XAML files rather than a XAML+.NET application class combination. By default EID (interactive designer) automatically creates a .xaml.cs file associated with any new scene. One approach to allow you to create standalone XAML files that I have found to work with the September CTP of EID is to:
- Remove the <x:Class> markup from the XAML header and
- Remove the .xaml.cs file from the project.
After these steps you can edit the standalone XAML file in EID and still be able to load it in more runtime oriented XAML environments.