dansiegel
commented
11 months ago Is this an oversight?
No... more like a limitation of the command line. Also it would be really helpful if you could provide more context like what name(s) are you trying. What version of the VS Extension are you using? What version of the .NET Templates are you using?
Remember that we had issues with certain characters being part of the template previously. This should mostly be fixed with regards to the template itself, although some characters like white space in the project name cause the Uno Xaml Generator to fail.
mrlacey
Current behavior
When creating a project from the templates in Visual Studio, there is a check for which characters are acceptable as part of the project (or solution) name
There's no equivalent test for the project name when creating a solution from the command line. Is this an oversight?
This means it's possible to create apps that won't build, and there's no obvious indication of what's wrong from the error messages that are produced. I understand that limiting the characters accepted avoids the need to deal with safe project names and escape characters, but I wanted to draw attention to the fact that these custom rules aren't being applied consistently when projects are being created outside of VS.
Expected behavior
Characters that are valid as part of a project name can be used, regardless of whether the wizard is used or the templates are used from the command line.
How to reproduce it (as minimally and precisely as possible)
Environment
Nuget Package:
Package Version(s):
Affected platform(s):
Visual Studio:
Relevant plugins:
Anything else we need to know?
The equals sign is technically valid as part of a project name but currently breaks on .net 8 due to https://github.com/dotnet/roslyn/issues/71022