Bug 37551 - Related files are not resolved
Summary: Related files are not resolved
Status: NEW
Alias: None
Product: Tools
Classification: Mono
Component: xbuild ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-01-09 23:56 UTC by Bruce Weirdan
Modified: 2016-01-09 23:56 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 37551 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description Bruce Weirdan 2016-01-09 23:56:37 UTC
When using ResolveAssemblyReference xbuild task related files are only resolved if you pass assemblies as AssemblyFiles, but are not resolved if you supply them in Assemblies parameter.

The following project file fails to display '.dll.config' and '.dll.pdb' files (both related to Mono.TextEditor.dll):

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Show" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <Import Project="$(MSBuildBinPath)\Microsoft.Common.tasks"/>
    <Target Name="Build">
        <ResolveAssemblyReference
            Assemblies="Mono.TextEditor"
            SearchPaths="/usr/lib/monodevelop/bin"
            AllowedAssemblyExtensions=".dll"
            AllowedRelatedFileExtensions=".dll.config;.dll.pdb"
            FindRelatedFiles="true"
            FindDependencies="true"
        >
            <Output TaskParameter="RelatedFiles" ItemName="ReferenceRelatedPath"/>
            <Output TaskParameter="ResolvedFiles" ItemName="ReferencePath"/>
        </ResolveAssemblyReference>
    </Target>
    <Target Name="Show" DependsOnTargets="Build">
        <Message Text="@(ReferenceRelatedPath)"/>
        <Message Text="@(ReferencePath)"/>
    </Target>
</Project>

It shows
/usr/lib/monodevelop/bin/Mono.TextEditor.dll
(missing related files)

If you replace Assemblies parameter with 
            AssemblyFiles="/usr/lib/monodevelop/bin/Mono.TextEditor.dll"

it correctly shows two related files:

/usr/lib/monodevelop/bin/Mono.TextEditor.dll.config;/usr/lib/monodevelop/bin/Mono.TextEditor.dll.pdb
/usr/lib/monodevelop/bin/Mono.TextEditor.dll


This makes it hard to use Private=true assemblies, because .config files often contain .dll -> .so mappings that are required to run application under mono/linux, and should thus be copied to output folder.