Writing a design time experience for a Silverlight control can be a bit intimidating (the experience for WPF controls remains unchanged from Blend 2 - just that you now have a ton more extensibility points - unless you wanted to re-use the same design-time code for the WPF and Silverlight versions of your controls). Let's try and understand how this works (because once you know the basics, its a breeze!).
Here is a project template that will help you get started immediately. All you need to do to use this project template is to unzip the contents to a folder like C:\Users\<username>\Documents\Expression\Blend 3\ProjectTemplates. Also, sorry - I did not have time to create a VB version yet.
The project created from this project template works as follows:
While there are clear benefits to the approach we have chosen to support both WPF and Silverlight controls (same extensibility APIs so you don't have to learn two sets of APIs, ability to reuse the code for your design time experiences for WPF and Silverlight version of your controls by simply creating platform specific versions of the design time libraries), there are some pitfalls for advanced scenarios that can be easily avoided:
Enjoy, and please do let me know if you run into issues as you work with Silverlight design time experiences so we can address them.
PingBack from http://www.anith.com/?p=21589
windows ce support in blend, nice :)
Seems that the link does not work
Oops, the link should be the following: http://home.comcast.net/~unnir/samples/SilverlightClassLibraryWithDesign.zip
You know the drill. Raw/unedited conversations from our internal discussions.  Subject: Datagrid