All of my cross-platform libraries are created with solutions that have two projects: one that builds on the Silverlight CLR and one on the regular CLR. Hence, every library I make has two DLLs: name.dll and nameSilverlight.dll.
This is, as far as I know today, the only way to do it.
However, I recently tried Mike Talbot’s “Silverlight Serializer” DLL, and I could include the same DLL in a C# desktop and in a Silverlight application. It’s the exact same file.
How did he do that? And how can I do that?
(I really need to do it, because I’m trying to serialize in a desktop app and deserialize in a Silverlight app, and the assemblies are not matching up because they’re different.)
Silverlight 3 is a “lowest common denominator” and if you just use base/core classes, you can compile a DLL there and reference it directly from .NET. You cannot, without the portable library, do the converse however.