I just did a quick test... If you try to add a reference to a .NET 4 project from a SL4 project it says: "You can only add project references to other Silverlight projects in the solution".
If I try to add a reference to a SL4 project from a .NET 4 project it works OK. I can also instantiate a class from the SL4 library - compiles fine. So it looks like "same compiled code" means all your shared code has to be in SL libraries, if you want to share it. Disappointing that you can't use "full" CLR libraries from "silverlight" CLR, but I am sure there is a good technical reason (SL CLR subset of full CLR?). It's certainly a bit of a confusing claim - I have not seen a clear explanation of it anywhere. On Fri, Dec 4, 2009 at 1:51 PM, Stephen Price <[email protected]>wrote: > "The .NET Common Runtime (CLR) now enables the same compiled code to be run > on the desktop and Silverlight without change." > > Just curious if anyone has tested this out to see what it actually means? > The way I read it, I should be able to compile my dll, then reference it in > a normal .Net project and make calls to it (such as unit tests). > Or is it saying that .Net code/assemblies can be run in Silverlight without > change? (ie Silverlight now has a full CLR implementation?) > ...or something else? > > cheers, > Stephen > > _______________________________________________ > ozsilverlight mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > >
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
