Bug 42783 - The target "GetBuiltProjectOutputRecursive" does not exist in the project
Summary: The target "GetBuiltProjectOutputRecursive" does not exist in the project
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Installer ()
Version: 4.1.0 (C7)
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-07-25 14:12 UTC by John Miller [MSFT]
Modified: 2016-12-27 22:05 UTC (History)
5 users (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 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.

Related Links:
Status:
RESOLVED NOT_REPRODUCIBLE

Description John Miller [MSFT] 2016-07-25 14:12:37 UTC
**Overview:**

   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
   - Build

**Actual Results:**

   The target "GetBuiltProjectOutputRecursive" does not exist in the project.

**Expected Results:**

   No build errors. 

**Build Date & Platform:**

   VS 2015, Cycle 7 Stable

**Additional Information:**

   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:

%ProgramFiles(x86)%\MSBuild\14.0\Microsoft.Common.targets\ImportAfter\Xamarin.Common.targets
%ProgramFiles(x86)%\MSBuild\12.0\Microsoft.Common.targets\ImportAfter\Xamarin.Common.targets
%ProgramFiles(x86)%\MSBuild\11.0\Microsoft.Common.targets\ImportAfter\Xamarin.Common.targets
%ProgramFiles(x86)%\MSBuild\4.0\Microsoft.Common.targets\ImportAfter\Xamarin.Common.targets
%ProgramFiles(x86)%\MSBuild\Novell\MonoDroid.FSharp.targets
%ProgramFiles(x86)%\MSBuild\Novell\Novell.MonoDroid.Common.targets
%ProgramFiles(x86)%\MSBuild\Novell\Novell.MonoDroid.CSharp.targets
%ProgramFiles(x86)%\MSBuild\Novell\Xamarin.Android.Bindings.targets
%ProgramFiles(x86)%\MSBuild\Novell\Xamarin.Android.VisualBasic.targets
%ProgramFiles(x86)%\MSBuild\Xamarin\updateinfo.dat
%ProgramFiles(x86)%\MSBuild\Xamarin\Xamarin.ObjcBinding.CSharp.targets
%ProgramFiles(x86)%\MSBuild\Xamarin\Android\
%ProgramFiles(x86)%\MSBuild\Xamarin\iOS\
%ProgramFiles(x86)%\MSBuild\Xamarin\TVOS\
%ProgramFiles(x86)%\MSBuild\Xamarin\WatchOS\

It seems that a targets file is not getting updated/removed for unknown reasons.
Comment 1 Ben Beckley 2016-07-26 18:26:55 UTC
Hi John,

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?
Comment 3 Jose Gallardo 2016-12-27 22:05:55 UTC
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.
Thanks!