Bug 12064 - Cannot start debuggin when "Platform" is different from "AnyCPU"
Summary: Cannot start debuggin when "Platform" is different from "AnyCPU"
Status: RESOLVED DUPLICATE of bug 11977
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.8.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-05-01 20:05 UTC by Val Savvateev
Modified: 2013-05-03 19:31 UTC (History)
1 user (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 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:
Status:
RESOLVED DUPLICATE of bug 11977

Description Val Savvateev 2013-05-01 20:05:25 UTC
We renamed the platform from "AnyCPU" to "Android". Now when we try to run the app in debug mode Xamarin studio breaks with error:

"Intermediate manifest file is missing"

This perhaps could be related to 11977, because we noticed that changing the platform name implicitly changes the obj path (the platform name becomes part of the path, even though we don't specify for that to happen anywhere)
Comment 1 Mikayla Hutchinson [MSFT] 2013-05-03 19:31:39 UTC
Yes, this should have been fixed by the fix for bug 11977.

*** This bug has been marked as a duplicate of bug 11977 ***