Bug 1719 - Different project name and output assembly name can cause symbolication to fail
Summary: Different project name and output assembly name can cause symbolication to fail
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 2.8.1
Hardware: PC Windows
: Low minor
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2011-10-27 09:05 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2015-01-12 17:38 UTC (History)
3 users (show)

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:

Description Rolf Bjarne Kvinge [MSFT] 2011-10-27 09:05:27 UTC
If a project name and the output assembly names are different, it will result in outputting of XX.app and XX.app.dSYM, (matching project name) but results on other items with different naming, e.g., XXIPhone.exe, XXIPhone.exe.mdb, XXIPhone.xcent and the crash logs come out prefixed as XXIPhone_. This all functions just fine, but some internal naming differences causes the symbolication of the crash log to fail.
Comment 2 Mikayla Hutchinson [MSFT] 2011-10-27 09:15:03 UTC
Maybe we should use output name as the app name. I think using project name may have been a mistake. But it would be difficult to make that change without breaking things.
Comment 3 Jeffrey Stedfast 2015-01-12 17:38:54 UTC
this has been implemented.