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 for Bug 20963 on
Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
The values for a widget's Identity "Name" and "Class" that a user may enter using the Properties window should only allow for valid file names, class names and property names.
For example if you enter today "1Foo" in the "Class" field, you get no warning by the Properties window that this value is invalid and you should change it.
The designer will allow this "1Foo" value to be entered and will end up generating code (a class in this case) that won't compile.
Visual Studio users are used to get an error dialog as soon as their enter an invalid value for a property value. This is usually implemented by using TypeConverters that check the entered data.
On entering "1Foo" in the "Class" field, no warning is shown by the Properties window that this value is invalid.
Xamarin 184.108.40.206 (09870684ffab6d8697b491503867808b567b4021)
*** Bug 33129 has been marked as a duplicate of this bug. ***
In a derivative form of this, I was able to create a Class with a line break in it. Originally, it happened from some sort of delay with the Designer reloading, but you can reproduce it by copying text with line breaks from a text editor into the Class property field.
Xamarin Studio successfully created files with line breaks in them on the Mac. If the line break is at the end of the class name, even the generated C# file is valid. (If not, you split the class name and it won't build as above.) When that resulting project is loaded on Visual Studio, it will crash when you try to see the files in the Solution Explorer.