>>Another coincidence :-}
>>
>>I've also been working recently on importing Adobe Illustrator into XAML.
>>
>>I tried Mike Swanson's add-in. It produced nicely sparse XAML but missed out handling some stuff like images so in the end it wasn't a complete enough implementation
>>
>>I also looked at an open-source solution (can't find the link at the moment) . Again far from complete but, since the source code was available, I figured maybe I could work on the missing bits that I needed. Big snag there turned out to be finding any clear documentation from Adobe on the document structures.
>>
>>But now EB3 includes Illustrator file imports out of the box (with the most complete implementation I found) so I'm using that (or at least the design guys are)
>>
>>My biggest bitch with all of the above was that the import process made no attempt to convert from the Illustrator 72dpi format to the WPF 96dpi. Don't know what possessed them all to assume that I'd be happy with a drawing at 2/3rds of its designed size. I ended up writing a small prog to parse the XAML and rewrite all of the values. Also took the opportunity to automatically chop out some redundant XAML produced by the conversion.
>>
>
>I'm working on a tool for working with the outputs. I just scrapped my first version of it and rewrote it a few weeks ago. But I'm designing it to be a full resource manager. that allows me to extract and copy resources between XAML files. Standardize colors, transform and combine primitives etc. I'm also putting some basic editing abilities into it.
>
>It's a side project, but it's coming along.

Sounds interesting. So are you using Mike Swansons add-in to get the initial XAML files? I exchanged a couple of emails with him and it seems he basically produced the tool as an exercise and no longer intends adding any more functionality.

This is the link I couldn't find for the other option :http://www.codeplex.com/wikipage?ProjectName=xamlxporter . But I still haven't found any good quality documentation on the .ai format so extending it could be a nightmare - I'll stick with ExpressionBlend for the time being.