Bug 11073 - MonoDevelop cannot resolve reference when using TokenReplacement in HintPath
Summary: MonoDevelop cannot resolve reference when using TokenReplacement in HintPath
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-03-12 11:43 UTC by borrillis
Modified: 2013-03-12 18:29 UTC (History)
1 user (show)

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 on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description borrillis 2013-03-12 11:43:53 UTC
I have the following Reference in my .csproj file which works in VS201*, but MonoDevelop fails to find the reference

    <Reference Include="Ionic.Zip">

If I re-Add the reference using MonoDevelop it created the following entry, which obviously works.

    <Reference Include="Ionic.Zip.Axiom">

IF I change it to this:

    <Reference Include="Ionic.Zip.Axiom">

It no longer works again.
If I change my original entry to
    <Reference Include="Ionic.Zip">

It works correctly, but changes the alias (Include="") to the name of the assembly.
Comment 1 Mikayla Hutchinson [MSFT] 2013-03-12 18:29:08 UTC
This will work if you enabled experimental xbuild/msbuild build engine. It will be fixed when the xbuild/msbuild build engine is used by default.

For a fuller explanation, see http://mjhutchinson.com/journal/2012/08/19/state_msbuild_support_monodevelop