Thursday, December 17, 2009
« Vertigo announces Portland office | Main | Mike Downey at Portland Silverlight User... »
Found System.Xml.Linq for Silverlight 4 Beta

The Silverlight 4 Beta does not install the System.Xml.Linq.dll assembly into C:\Program Files (x86)\Microsoft Silverlight\4.0.41108.0 along side the rest Silverlight 4 assemblies. It’s okay, it’s a beta: “You knew the job was dangerous when you took it, Fred.”

The good news is that the assembly is installed in the C:\Program Files (x86)\Microsoft SDKs\Silverlight\v4.0\Libraries\Client folder. So when adding a reference to System.Xml.Linq in a Silverlight application, just browse to the assembly in this folder and you’re off to the races.

(On 32-bit systems, replace C:\Program Files (x86) with C:\Program Files. But you knew that.)

Silverlight
Thursday, December 17, 2009 6:46:21 AM (Pacific Standard Time, UTC-08:00)  #    Disclaimer  |  Comments [2]  |  Related posts:
Vote for my poem, help me win
Vertigo announces Portland office
Seattle Silverlight User Group launches this week
Portland Silverlight User Group nudge
Portland Silverlight User Group launches with a splash
Portland Silverlight User Group announced
Thursday, December 17, 2009 11:13:52 AM (Pacific Standard Time, UTC-08:00)
Hey Stuart. I'd expect this to remain the same for RTW of Silverlight 4.
The C:\Program Files (x86)\Microsoft Silverlight\4.0.41108.0 contains the assemblies that are part of the plugin. With these, Copy Local is set to false, and they are *not* packaged in the .xap. Instead, we can rely on them existing on the client machine.

The SDK folder contains system libraries that *are* packaged into the .xap. They don't exist on the client machine, and for these, Copy Local is set to true. This is done to keep the download size of the Silverlight plugin to a minimum.

System.Xml.Linq.dll has been one of the SDK .dlls in 2 and 3, and I'd expect it to keep its home in the SDK folder.
Erik Mork
Monday, December 28, 2009 5:07:50 PM (Pacific Standard Time, UTC-08:00)
That's good information and it makes sense, too. Thanks. In that case, I'd say that the Add Reference dialog for Silverlight projects should be smart enough to know about both of these locations instead of making the user track them down. In a SL project, when I select Add Referece, the .NET tab lists no components at all.
Visual Stuart
Comments are closed.