Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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
GitHub or Developer Community 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.
1) Create a new C# project that references an old version of a NuGet package that contains custom MSBuild targets or properties files (e.g. 'Test.Import.Foo').
2) Run/Debug nuget update on this project.
3) The old .targets/.props references should be removed from the project.
3) The old .targets/.props are still there.
The problem is that NuGet compares the Project part of the Import element using the wrong path separate.
So it will be looking for "packages/Test.Import.Foo.0.5/build/Test.Import.Foo.targets" which does not exist. The code doing this check is:
I believe that a change should be made to NuGet to fix this. MSBuild projects should use backslash for path separators regardless of the operating system. So NuGet should convert the original path.
Note: This has been logged under the Product: Tools, Component: Other. It may need to go somewhere else. Maybe Component: NuGet ?
Please report this issue upstream