Unity 3.5 RTW: Now with more Peace, Love, and Rock ‘n’ Roll

I’m extremely proud to announce the latest release of the Unity DI container. We have updated it to simplify cross-platform development of apps and services. While this 3.5 release is filled with too many improvements to talk about, I’d like to highlight these two:

  • Truly portable class library: We have transformed the individual platform targeted Unity into a PCL, including support for Windows Store Apps 8.0 and 8.1, Windows Phone Silverlight 8.0 and 8.1, .NET 4.5 and up, and new with this release is support for Xamarin/Mono (Xamarin.iOS v7 and Xamarin.Android v4.12). Xamarin support is significant as it makes Unity a truly portable class library, making it simple for C# developers to share code across devices.
  • Performance improvements: We have streamlined the internals of Unity without impacting the public-facing API. In running micro-benchmarks, we have consistently seen a performance improvement of Unity core operations by ~60%. We encourage you to do your own perf testing and additionally validate our findings with your data.

The official release notes are available from here.

Grab the binaries from NuGet.

Enjoy this release of Unity and remember to send us your pull requests if you have ideas on how to improve it.

Comments (5)
  1. Andrey Mamontov says:

    I got strange error massage by start using Unity on Xamarin.iOS envirement

    Missing method System.Linq.Expressions.Expression::IfThen(Expression,Expression) in assembly /Developer/MonoTouch/usr/lib/mono/2.1/System.Core.dll, referenced in assembly …/packages/Unity.3.5.1404.0/lib/portable-net45+wp80+win8+MonoAndroid10+MonoTouch10/Microsoft.Practices.Unity.dll

  2. Christopher Bennage says:

    If any one is interested in support for Windows Phone 8.1, we now have a pre-release available:


  3. Dzmitry.Lahoda says:

    Cool. Not I will try to cut out Mono reflection API and port Unity to .NET 4.0.

  4. Carlos Adriano Portes says:

    Make sure you are using the latest assemblies, I had this problem once and later discovered one of my assemblies were outdated.

  5. dzmitry.lahoda says:

    Port to 4.0 seems here


Comments are closed.

Skip to main content