2 Answers, 1 is accepted
0
Accepted
Hi Rick Glos,
Miro Miroslavov
the Telerik team
You are correct that Visual Studio automatically copies the referenced assemblies to the output directory, but only if it detects that something from that assembly reference chain is used. You can check the attached example project for that. However the problem here is that Visual Studio do Not detects the usages in Xaml, so it doesn't copy some of the assemblies to the output dir, thus the application crashes at run-time.
You can test this by removing the line that instantiate Class1 in the WPF app and instead create instance in xaml like <classlibrary1:Class1 />. The second way it won't copy the assemblies to the output dir.
Hope this help you.
Miro Miroslavov
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Rick Glos
Top achievements
Rank 1
Rank 1
answered on 16 Sep 2010, 06:54 PM
Yes thank you Miro. I did not know this.
Another way I thought of to get this 'code-behind' hack to work was to add a Name element to the control so it would then create the stronger reference in the UserControl1.g.cs generated file. That way I don't have to instantiate a class in the code-behind. But really, either way works.
Anyway, thanks again.
Another way I thought of to get this 'code-behind' hack to work was to add a Name element to the control so it would then create the stronger reference in the UserControl1.g.cs generated file. That way I don't have to instantiate a class in the code-behind. But really, either way works.
<telerik:RadButton x:Name="RadButtonTest" Content="Test"></telerik:RadButton>Anyway, thanks again.