Search

Data export from DataGrid to Excel is very common task, and it can be solved with different ways, and chosen way depend on kind of app which you are design. If you are developing app for enterprise, and it will be installed on several computes, then you can to advance a claim (system requirements) with which your app will be work for client. Or customer will advance system requirements on which your app should work. In this case you can use COM for export (use infrastructure of Excel or OpenOffice). This approach will give you much more flexibility and give you possibility to use all features of Excel app.

This project creates a fully "Designable" Silverlight Video Player. This is not to be confused with a "Skinable" Video Player. A Skinable Video Player allows you to change the look and feel of the existing controls of the Video Player. A Designable player, allows a Designer to use ANY set of controls to implement the Video Player. For example, a Designer could replace all the buttons with a single dial that a user rotated into different positions, or they could change the method a user uses to select from the list of available videos. This can be done in Expression Blend without writing any code.

I have just released a new version of WF(2)XAML. In this version (0.6 BETA) i have implemented the following changes:

• Added support for different destination projects
  • WPF User Control
  • WPF Window
  • WPF Page
  • Silverlight User Control
  • Windows Phone Navigation Page
• Changes in config file [...]

With Silverlight 4 trusted applications, the update mechanism requires that your applications be signed in order to use the auto-update APIs.  We wanted to wait until SL4 released in order to provide a signed version (and our internal signing process didn’t allow signing the beta).  Now that we have a signed version, you’ll be prompted when an update has been installed for the app.  

You’ve written your service. You’ve written your Silverlight application. You Add Service Reference to your application and got the client proxy code. Your app ‘works on your machine’ and you push it out. 

FAIL. NotFound.

Crap. You forgot that your service reference had your local URI endpoint in there and when you moved it to staging and/or production it failed.

In the comments of my Silverlight unemployment visualization, someone asked about where I got the US outline. I got it from theWikiCommons website which has an SVG (scalable vector graphics) version that I pulled into Adobe Illustrator and then exported as a XAML file using Mike Swanson’s Illustrator-to-XAML plugin. I realized this might not be possible for many people who don’t own Adobe Illustrator, so I did it myself for several files that are now available for download as XAML vector graphics maps of the US.

In Silverlight 4, more than a year of development went into a modern, improved parser to offer new XAML features, fix some common requests and complaints, and develop a modern platform for future parser improvements to build upon.

A number of expert engineers at Microsoft came together to make this possible, and hopefully you’ll find the improvements worthwhile.

This prefix provides a common URI-based XAML namespace that ALL of the most commonly used client SDK controls can share.

Let's have a look at how this worked before, in Silverlight 3 (and in the Silverlight 4 beta, for that matter).