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
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.
Some users are reporting a build error on existing projects in VS 2015 after updating Xamarin tooling to use VS 2015 from VS 2013.
**Steps to Reproduce:**
This is unclear. However, it seems common that it's something like this:
- Use VS 2013 with an older version of Xamarin (pre-licensing change?)
- Install VS 2015
- Update Xamarin tooling to be able to use VS 2015
- Open existing solution from step 1 in VS 2015
The target "GetBuiltProjectOutputRecursive" does not exist in the project.
No build errors.
**Build Date & Platform:**
VS 2015, Cycle 7 Stable
The best workaround we have found is to follow this guide: https://developer.xamarin.com/guides/cross-platform/getting_started/installation/uninstalling_xamarin/#Uninstalling_Xamarin_on_Windows
Then, before reinstalling, verify that these are deleted:
It seems that a targets file is not getting updated/removed for unknown reasons.
I tried to reproduce this with guidance from the reproduction steps.
- Installed VS 2013 with XVS c6 baseline
- Created an XI project
- Installed VS 2015
- Installed XVS c7sr0
- Opened earlier XI project and built it successfully
Could you perhaps link to the user reports that document this issue?
We couldn't reproduce this issue.
Ben, did you manage to have a consistent repro with latest bits?
Even if there was an issue upgrading to the new licensing schema while updating VS, I don't think there is anything actionable at this point on this bug, so I'm moving it tentatively as Resolved / Not_Reproducible.
That said, if any of you see anything we can do, please feel free to reopen it and let us know.