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.
Created attachment 20316 [details]
Xamarin Logs and Stacktrace of build ooutput
On building tvos.debugging app, the build is failing with following error
"The target "GetBuiltProjectOutputRecursive" does not exist in the project. tvOS.Debugging"
Environment : Microsoft Visual Studio Professional 2013
Version 12.0.40629.00 Update 5
OS : Windows 10
Xamarin 188.8.131.529 (4d2ed3d)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 184.108.40.206 (3a62f1e)
Visual Studio extension to enable development for Xamarin.Android.
Xamarin.iOS 10.4.0.128 (ba11e48)
Visual Studio extension to enable development for Xamarin.iOS.
Sample Used : QualityAssurance/Manual/CrossPlatformDebugging/CrossPlatformDebugging.sln
Steps to Reproduce:
1. Open CrossPlatformDebugging.sln Solution
2. Build entire solution
Application should build successfully without errors
Build Error Observed on building "The target "GetBuiltProjectOutputRecursive" does not exist in the project. tvOS.Debugging"
Screencast Link : http://www.screencast.com/t/qm8zIP8pDq
Attached : Xamarin Logs and Stacktrace of build ooutput
*** Bug 53374 has been marked as a duplicate of this bug. ***
This Issue was only observed in VS 13[Windows 10].
Thanks for the update, We will follow this going ahead.
This bug has been fixed in 4.5 (we don't use that target anymore). Resolving as Fixed for verification. Please reopen if you're still experiencing the issue.