Browse files

INCR to v3.9.29

  • Loading branch information...
1 parent b85e1b6 commit 41f57ed92496fa98ee5b5f6d9df1b4e35d2fc5db @mythz mythz committed Dec 7, 2012
@@ -3,7 +3,7 @@
<metadata xmlns="">
<title>.NET's fastest JSON Serializer by ServiceStack</title>
- <version>3.9.28</version>
+ <version>3.9.29</version>
<authors>Demis Bellot</authors>
<owners>Demis Bellot</owners>
<summary>.NET's fastest JSON, JSV and CSV Text Serializers (3x faster than JSON.NET)</summary>
@@ -23,7 +23,7 @@ static Env()
+ (IsMonoTouch ? " MonoTouch" : "");
- public static decimal ServiceStackVersion = 3.928m;
+ public static decimal ServiceStackVersion = 3.929m;
public static bool IsUnix { get; set; }
@@ -31,5 +31,5 @@
// You can specify all the values or you can default the Build and Revision Numbers
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
-[assembly: AssemblyVersion("")]
+[assembly: AssemblyVersion("")]
//[assembly: AssemblyFileVersion("")]

3 comments on commit 41f57ed

Jozzle commented on 41f57ed Dec 7, 2012

Hi there!

First of all, my compliments for this amizing library! It has already been a valued performance upgrade for our application 👍

I've pulled ServiceStack.Text version 3.9.29 from nuget (for a SilverLight 5 project) and am experience the following trying to also implement it for JSon objects using polimorphism:

The following two tests fail;

public void Can_deserialise_polymorphic_item_with_nonabstract_base_deserializes_derived_properties_correctly()
public void Can_force_specific_TypeInfo()

And a method 'IncludeTypeInfo' (JsConfig.IncludeTypeInfo = true;), doesn't seem to be available at all.

(referencing to test:

Am i missing something here? Does the Silverlight library not support polymorphism?

New to GitHub, so please accept my apologies if this is not the place for my question.



mythz commented on 41f57ed Dec 9, 2012

Hi Jozzle,

The Silverlight library is maintained by the ServiceStack Silverlight contributors which they tend to fix builds and maintain when they update their clients.

Ideally the Silverlight builds should support all the features that the base library does, albeit using slower workarounds when don't exist in full .NET. As it's not maintained by the core team (who don't even have Silverlight installed) it's common for Silverlight builds to slip behind the builds of the other platforms.

Jozzle commented on 41f57ed Dec 10, 2012

Thanks for clearing that up!

I really admire & am gratefull for all the work done here.



Please sign in to comment.