Bug 22087 - Xamarin.Mac (also .iOS) mangles project names for output locations/artifacts.
Summary: Xamarin.Mac (also .iOS) mangles project names for output locations/artifacts.
Status: RESOLVED DUPLICATE of bug 22116
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Other ()
Version: Master
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Chris Hamons
URL:
Depends on:
Blocks:
 
Reported: 2014-08-14 00:44 UTC by Brian Berry
Modified: 2014-08-14 13:24 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 22116

Description Brian Berry 2014-08-14 00:44:29 UTC
Found: For project names in families like "Test.iOS" and "Test.Android"
       and "Test.OSX", Xamarin.Mac is now mangling artifact locations/names.

E.g., you now end up with a TestOSX.app instead of Test.OSX.app.

Xamarin.Mac 1.11.0.1, also Xamarin.iOS current and for at least some time now.

Xamarin.iOS has also been doing this, but it even aliases the assembly bits as well.
Xamarin.Android does not mangle these names---you end up with a clean, precise honoring
of compound names all the way to the .apk and within.

The main issue here is inconsistency --- I've had to author one-off add-in and scripting
bits to essentially chase naming convention changes in the Xamarin toolchain.
It'd be helpful if a project of a given name has that name honored precisely
and consistently (as reported by the add-in project name property) no matter
the context, wherever possible.
Comment 1 Brian Berry 2014-08-14 13:24:27 UTC
Sorry, I filed a better one under https://bugzilla.xamarin.com/show_bug.cgi?id=22116, which indicates the more severe consequence of failed builds.

I'll mark this as a duplicate.
Comment 2 Brian Berry 2014-08-14 13:24:42 UTC

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