Assemblies built in Silverlight 2 and 3 are not binary compatible with the .NET Framework, so if you want to share code you need generally need to dual-compile. With Siverlight 4 and .NET 4, you will be able to use some Silverlight-based assemblies from within .NET 4.
In order to load a Silverlight assembly in .NET, the assembly may only reference the following assemblies:
- Mscorlib
- System
- System.Core
- System.ComponentModel.Composition
- Microsoft.VisualBasic
Other assemblies such as System.Xml and System.Net are not currently supported, nor are any of the UI libraries. This means sharing passive data objects is possible but active records that can call services or handle their own XML serialization are out of the question.
One should also note that loading .NET assemblies in Silverlight is explicitly not supported. Since the non-UI parts of Silverlight are a directly subset of .NET, they felt it was less error prone to do it this way than to try to deal with countless missing classes and methods.
If you would like to learn more about assembly portability or want to report an incompatibility between Silverlight and .NET, you can do so on the CLR Team blog.
/filters:no_upscale()/sponsorship/topic/25afca57-6bcb-4c42-9a70-fbea10ce4fc7/MicrosoftLogoRSB-1678874949003.png)
/articles/dotnet-spa-templates-proxy/en/smallimage/ASP-NET-SPA-templates-proxy-changes-small-1683016303172.jpg)
/presentations/net-apps-cloud/en/smallimage/infoq-live-logo-small-1683100880551.jpg){kind=logo}
/articles/asp-dotnet-minimal-apis/en/smallimage/logo-1678972581766.jpg){kind=logo}
/articles/functional-dotnet-development/en/smallimage/Fsharp-vs-Csharp-is-one-more-functional-than-the-other-small-1676023056578.jpg)
/articles/dotnet-grpc-json-transcoding/en/smallimage/logo-1674822319367.jpg){kind=logo}
/articles/Dotnet-Seven-MSMQ-Alternatives/en/smallimage/logo-1670585778128.jpg){kind=logo}
/articles/kafka-clusters-cloudflare/en/smallimage/tales-of-Kafka-at-Cloudflare-small-1684768928637.jpg)
/presentations/refactoring-cleaning-code/en/smallimage/kent-beck-small-1684908700538.jpg)
/presentations/devsusops/en/smallimage/adrian-cockcroft-small-1684908390875.jpg)
/articles/gdpr-with-spring-and-aop/en/smallimage/easy-implementation-of-GDPR-with-aspect-oriented-programming-small-1684505109873.jpg)
/articles/software-delivery-performance-indicators/en/smallimage/software-delivery-performance-indicators-at-different-granularities-small-1684312207072.jpg)
/articles/api-design-review/en/smallimage/API-design-reviews-are-dead-long-live-API-design-reviews-small-1684310900854.jpg)
/presentations/dark-energy-matter-microservices/en/smallimage/chris-richardson-small-1684240727275.jpg)
/presentations/techno-solutionism-ethics/en/smallimage/katharine-jarmul-small-1684239823523.jpg)
Community comments
Silverlight 2 and 3 assemblies ARE binary compatible
by Jason Young,
Re: Silverlight 2 and 3 assemblies ARE binary compatible
by Jonathan Allen,
Silverlight 2 and 3 assemblies ARE binary compatible
by Jason Young,
Your message is awaiting moderation. Thank you for participating in the discussion.
Silverlight 2 and 3 assemblies ARE binary compatible with the .NET framework 3.5, there are a few limitations on which classes can be accessed as explained here blogs.imeta.co.uk/jyoung/archive/2009/07/21/729...
Re: Silverlight 2 and 3 assemblies ARE binary compatible
by Jonathan Allen,
Your message is awaiting moderation. Thank you for participating in the discussion.
Seems you are not alone in thinking that. Once I get an answer from Microsoft on this point I'll post a correction.