Bug 26041 - [Build] The app bundle name is based on the csproj name and not output assembly name
Summary: [Build] The app bundle name is based on the csproj name and not output assemb...
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Other ()
Version: 1.11.0
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: 1.12.0
Assignee: Chris Hamons
Depends on:
Reported: 2015-01-14 17:22 UTC by Stephen Shaw
Modified: 2015-01-15 01:49 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 Stephen Shaw 2015-01-14 17:22:05 UTC
The app bundle appears to be based on the name of the project. If I have a project named MyApp.Mac, but my output->Assembly Name is "My App" Xamarin studio will build, but can execute it. It outputs in the bin/Debug directory MyAppMac.app.

So, I'll have
My App.exe

If I were to rename that project to MyApp.Mac2 I'd get:
My App.exe

Long and short of it is that at some point the output-assembly name in the project settings is ignored when generating the app bundle.
Comment 1 Stephen Shaw 2015-01-14 17:22:48 UTC
This is using Xamarin.Mac and on unified. I don't believe this is an issue with classic.
Comment 2 Chris Hamons 2015-01-14 18:44:58 UTC
This is fixed with maccore / f86ff68d1f515d670795858c6195458a67a16794.

I have a request out for merging this into 1.12.