Bug 3203 - User is able to create a solution with invalid characters in name
Summary: User is able to create a solution with invalid characters in name
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8.6
Hardware: PC Mac OS
: Low enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-02-02 12:11 UTC by PJ
Modified: 2015-07-31 10:18 UTC (History)
3 users (show)

Tags: templating
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 PJ 2012-02-02 12:11:45 UTC
When creating a c# console project, using invalid characters results in a project that won't build.

I *was* able to get an iPhone single view template to run using a crazy gobbledygook name

Mono for Android solution with garbled name failed on package creation, but still allowed me to select a device and try to load the failed package.


Steps to reproduce:
1. Create a console project/MfA application project with the name
23t6&#%^<^>&@$!^^!<&>

2. Run
Comment 1 Miguel de Icaza [MSFT] 2012-02-14 13:15:07 UTC
Well known problem, with a long-term solution
Comment 2 Lluis Sanchez 2015-07-31 10:18:27 UTC
Already fixed.