Bug 4239 - MonoDroid targets file cannot rely on RootNamespace existing
Summary: MonoDroid targets file cannot rely on RootNamespace existing
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-04-04 14:48 UTC by Alan McGovern
Modified: 2015-02-27 20:17 UTC (History)
3 users (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 FIXED

Description Alan McGovern 2012-04-04 14:48:29 UTC
It is valid for a user to remove the 'RootNamespace' element from their csproj file by clearing the value of 'Default Namespace' in the monodevelop project operations. The MonoDroid xbuild targets file needs to take this into account and not throw this error when building a project without this value. Maybe we could fall back to AssemblyName:


/Library/Frameworks/Mono.framework/External/xbuild/Novell/Novell.MonoDroid.Common.targets: Error: Error executing task GenerateResourceDesigner: Required property 'Namespace' not set.
Comment 1 Jonathan Pobst 2012-04-04 15:02:48 UTC
Already fixed.  :)

28a259147423ef6ddafc3e45de035d3d72f8097a