Skip to main content

SharpSerializer for Windows Phone 7

There's a new binary serializer available for WP7 - SharpSerializer. It 's OSS and is currently hosted on CodePlex. Available via NuGet as well.

I received an anonymous comment the other day on a blog post about serialisation performance on WP7. So I thought I would re-run the test app and see how it compared, the original post can be found here. My first attempt failed because the NuGet packages were invalid, so after the author had corrected this I decided to run the test again. This time though I got the latest code and explicitly compiled this as  a WP7 class library.

So I ran the same test, binary serialize a collection containing 1000 items and display the performance results to the output window in visual studio:


The results don't lie, sharpSerializer is good, but SilverlightSerializer still has it for me.

Good to see some competition in this space I'll be keeping an eye on this project.





Labels:

Comments

  1. Rene Schulte24 August 2011 at 11:11

    Nice, but it's not just about performance. I had some issues with OSS serializer using Dictionary or similar complex data types. Have you tested those aspects?

    ReplyDelete
  2. awkwardcoder24 August 2011 at 16:45

    It is when I am on the phone ;)

    But I see your point, SS is easily extensible

    ReplyDelete

Post a Comment

Popular posts from this blog

Showing a message box from a ViewModel in MVVM

I was doing a code review with a client last week for a WPF app using MVVM and they asked ' How can I show a message from the ViewModel? '. What follows is how I would (and have) solved the problem in the past. When I hear the words ' show a message... ' I instantly think you mean show a transient modal message box that requires the user input before continuing ' with something else ' - once the user has interacted with the message box it will disappear. The following solution only applies to this scenario. The first solution is the easiest but is very wrong from a separation perspective. It violates the ideas behind the Model-View-Controller pattern because it places View concerns inside the ViewModel - the ViewModel now knows about the type of the View and specifically it knows how to show a message box window: The second approach addresses this concern by introducing the idea of messaging\events between the ViewModel and the View. In the example ...
5 comments
Read more

WPF tips & tricks: Dispatcher thread performance

Not blogged for an age, and I received an email last week which provoked me back to life. It was a job spec for a WPF contract where they want help sorting out the performance of their app especially around grids and tabular data. I thought I'd shared some tips & tricks I've picked up along the way, these aren't probably going to solve any issues you might be having directly, but they might point you in the right direction when trying to find and resolve performance issues with a WPF app. First off, performance is something you shouldn't try and improve without evidence, and this means having evidence proving you've improved the performance - before & after metrics for example. Without this you're basically pissing into the wind, which can be fun from a developer point of view but bad for a project :) So, what do I mean by ' Dispatcher thread performance '? The 'dispatcher thread' or the 'UI thread' is probably the most ...
Post a Comment
Read more

Managing themes in WPF

Having just published Simple.Wpf.Terminal as a nuget package I wanted the ability to skin the user control - the more flexibility in the way it looks the more likely it will be used by other devs :) Before getting into the detail, lets look at the solution working in the test harness for my WPF F# REPL Engine , shown below are four different themes applied dynamically at run-time - no recompilation required to change the theme: Previously in larger WPF apps I've relied upon third-party control vendors like Telerik to provide theming support. Typically they provide good solutions to the problem with multiple themes supported as standard, and when you're already using their third party controls the use of their themes makes sense. But when you're developing a small UI component you don't want to add (& support) such a large footprint just to add themes to your niche control. A theme is a collection of Styles grouped into a ResourceDictionary in WPF. A ...
Post a Comment
Read more