C # / Silverlight: SL classlibrary that is referenced in a "normal" C # application, should Silverlight be installed?

So, I want to share TONS of code between Silverlight and "normal" applications. Starting with utility functions and everything up to my hand-coded structure (MVC, DI, etc) ...

Here's my question:

Imagine I included all this stuff in the SL-Classlibrary, called it "AmazingLibrary", and I link to it in a NORMAL project (say WPF) that doesn't use Silverlight ...

Should I get people to enjoy my WPF application to install Silverlight in the first place, or is the assembly "a little different but still works under normal CLR 3.5"?

+2


a source to share


1 answer


No, you don't need people to install SilverLight to use your external library. The SilverLight class library can simply reference a subset of what is in .net.

Here is a link describing the differences between the regular library and the SilverLight library:



http://www.scribd.com/doc/17088869/SilverLight-Class-Library-vs-Normal-Class-Library

+1


a source







All Articles