Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
[22:30:46] <spouliot> I closed the (novell) bug about it - want a new one (xamarin) for MD addin to disallow such thing ?
[22:31:32] <miguel_> I think we should get that in place
[22:31:35] <miguel_> Assign it to Alan
Original report: https://bugzilla.novell.com/show_bug.cgi?id=691193
I implemented this a while ago, though it might have got broken since.
If you look in IPhoneProjectConfiguration you'll see a SanitizeAppName that gets called when creating new configurations from IPhoneProject, and AppNameIsValid that gets called when compiling the project to emit an warning.
I suppose you could change the warning to an error, in which case you should probably do that for CheckContentNamePermitted and CheckInterfaceDefinitionNamePermitted too.
I tested the original bug report by renaming the application project inside MonoDevelop. Maybe that does not go thru the same validations ?
Possibly, yeah, though I didn't think we changed output names when renaming projects. You should have still hit the warning though.