msbuild and paths

[B]

Hi,

In Q3 for both Silverlight and WPF the dll's are copied twice for each project, why is that? For example:

C:\Development\GeneticsTools\PowerKladBlok\lib\RCWPF\2015.3.1104.45\Telerik.Windows.Controls.dll

This folder is also what I get when I create a new Telerik project from scratch, so this "RCWPF" folder is not something I could have created myself.

What is the purpose of this folder?

It causes problems with my build server, so I changed it back to the Roaming folder, but now I get a strange error after the build proces has completed:

Copying file
C:\Builds\2\PowerWebForms\Build Release\bin\PowerBrowser\PowerBrowser.xap
failed. No Silverlight project specified for Silverlight output
C:\Builds\2\PowerWebForms\Build Release\bin\PowerBrowser\PowerBrowser.xap.

And I can't figure out how to get rid of this error, it doesn't make sense to me, the xap itself seems fine. 

So I am not sure what is going on?

Am I not allowed to change the paths back to Roaming?

Does something special happen to these copies of the dll's?

Regards,

Bayram

 

[Yana]

Hi Bayram,

Thank you for contacting us.

Based on the provided details, it seems that when your project has been created the "Add referenced assemblies to solution" option has been checked. The "Add referenced assemblies to solution" option is used for choosing whether to copy referenced assemblies to your solution folder under the following structure: [Project location]\lib\RCWPF\[Product Version]. Moreover, the assemblies are automatically added to source control when using Microsoft Team Foundation Server.

You could easily uncheck the option so as to prevent adding the assemblies to your project's directory. Please take a look at the following documentation article for more details. 

Having deselected the "Add referenced assemblies to solution" option into the Options dialog, I would recommend you upgrade your project with our Upgrade wizard. In this way, all of the Telerik assemblies will be re-targeted to the UI for WPF/UI for SIlverlight distribution location. More information about how to take full advantage of our Upgrade wizard can be found in these articles: UI for WPF and UI for Silverlight.

Could you please try to perform my suggestions and let us know in case the issue still persists?

I am looking forward to your feedback.

Regards,
Yana
Telerik