Silverlight 2.0 assembly

[GoogleCodeExporter]

It would be great if the source was compilable for Silverlight deployment 
as well as regular .NET framework use. This should, in most cases, be as 
simple as using the same source and compiling for Silverlight.

Original issue reported on code.google.com by jeffma...@gmail.com on 18 Feb 2009 at 5:46

[GoogleCodeExporter]

I'm working on some Silverlight 2.0 projects and using LINQ quite a lot. It 
would be 
great to have MoreLINQ-to-Object support. I'll try compiling the source for 
this use 
and see if I encounter any issues - just wanted to raise as a placeholder while 
I 
remembered. I'll add a comment once I've given it a try with the current source.

Thanks all!

Original comment by jeffma...@gmail.com on 18 Feb 2009 at 5:47

[GoogleCodeExporter]

Original comment by azizatif on 19 Feb 2009 at 12:43

• Changed state: Accepted
• Added labels: Milestone-Release1.0

[GoogleCodeExporter]

Implemented in r46.

Original comment by azizatif on 19 Feb 2009 at 12:55

• Changed state: Fixed

[GoogleCodeExporter]

What does this mean, going forward? Does it require manual intervention every 
time we 
add a class? (And what exactly do I need to install to get it to load the 
project 
properly? :)

Original comment by jonathan.skeet on 19 Feb 2009 at 1:03

[GoogleCodeExporter]

> Does it require manual intervention every time we 
> add a class

If new files are added to the primary project but not the Silverlight one then 
its
harmless. Someone needs to sync up things at some point.

> what exactly do I need to install to get it to load the project 
> properly?

Point taken. :) We can resolve this by creating a second solution file that
references the Silverlight project and leaves the main one as it was previously.

Most of these concerns could be resolved with a continuous build server and 
script
where installation concerns and manual interventions surface quickly.

Original comment by azizatif on 19 Feb 2009 at 1:43

[GoogleCodeExporter]

> creating a second solution file that
> references the Silverlight project and leaves the main 
> one as it was previously.

Fixed in r47.

Original comment by azizatif on 19 Feb 2009 at 1:49

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Wow, quick turnaround. And Jon, to load the project properly I suspect you'd 
need the 
[http://msdn.microsoft.com/en-us/library/cc838244(VS.95).aspx Silverlight Tools 
for 
Visual Studio 2008].

Original comment by jeffma...@gmail.com on 19 Feb 2009 at 2:29