Just a follow-up:
I wrote a simple conversion app to make the generated xaml attributes Expression Blend friendly
After working with the objects exported to xml, I found myself not needing Blend
(Hope to see your WPF only products made available to Silverlight...)
ttiggemann, May I ask you what have you done to make the xaml Blend friendly.
I would like to add this to the my reader products, so there would not be a need for custom convertion applications.
ttiggemann, thank you for sharing this with us.
I will add an option to ViewerSvg, Paste2Xaml and GetXaml method in reader libraries to provide xaml that will be valid in Expression Blend.
VS2010 is not happy either:
"Unknown element: Brush. [Line: 1 Position: 93]
at MS.Internal.XcpImports.CreateFromXaml(String xamlString, Boolean createNamescope, Boolean requireDefaultNamespace, Boolean allowEventHandlers, Boolean expandTemplatesDuringParse)
at Microsoft.Expression.Platform.Silverlight.TypeConverters.ConvertUsingXamlReaderConverter`1.ConvertFromStringInternal(String value, IFormatProvider provider)
at Microsoft.Expression.Platform.Silverlight.TypeConverters.ConvertToFromStringConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at System.ComponentModel.TypeConverter.ConvertFromInvariantString(String text)
at Microsoft.Expression.DesignModel.InstanceBuilders.ClrObjectInstanceBuilder.InstantiateTargetType(IInstanceBuilderContext context, ViewNode viewNode)"
Is there an ETA of when your changes will be available?
Hm, this looks very critical.
I will try to prepare updates until the end of this week.
Finally got the chance to try your updates in v2.2
Looks great, works great!
"Add default namespaces" is certainly a timesaver
A couple of items on my "wish list":
The ability to name the top level node
The ability to specify a background color (mouse events are ignored if no background)