Link to the assembly in the Silverlight class library and is used only in xaml, not packaged in XAP

Question

I have a third-party library (A). This library is mentioned in my Silverlight (B) class library. This Silverlight class library is specified in a Silverlight (C) application. The third-party library is not explicitly specified in the Silverlight application.

It seems like “A” is being added to my XAP if “A” is used in any class in “B” because of the chain of dependencies (C → B → A). This behavior I would expect and need.

If "A" is never explicitly used in a C # class, but only defined in Xaml, the assembly is not packaged in XAP. Perhaps “A” includes a control that is used only declaratively and never refers to it.

Is this design behavior? Am I missing a property somewhere that controls this? I would rather not explicitly reference a third-party library in my Silverlight application. What is the best way to ensure that all required assemblies are packaged in XAP?

Answer 1

If you want to include a file in your XAP that is not explicitly specified, all you do is:

Visual Studio/Solution Explorer  1. , -/  2. " " DLL,  3. ,  4. "" ""  5. " " " "

XAP