You can't share assemblies between silverlight and the desktop clr as they are subtley different runtimes. Even if you use intrinsic types such as string, that is actually a binding to the system.string class in the respective runtime. Due to the string
typing of .net, it doesn't like trying to use one in the other.
Your solution of having 2 projects and sharing source between them is probably the cleanest.
The goal is to move from the hacked up json stack and support WCF as the web references stack for silverlight.
samsp
Member
282 Points
96 Posts
Microsoft
Re: Re: Re: Silverlight project "add reference"
Sep 14, 2007 06:12 PM | LINK
You can't share assemblies between silverlight and the desktop clr as they are subtley different runtimes. Even if you use intrinsic types such as string, that is actually a binding to the system.string class in the respective runtime. Due to the string typing of .net, it doesn't like trying to use one in the other.
Your solution of having 2 projects and sharing source between them is probably the cleanest.
The goal is to move from the hacked up json stack and support WCF as the web references stack for silverlight.