C# Add New Class is broken when RootNamespace is empty about templates HOT 9 OPEN

FYI. @srivatsn, @jaredpar

from templates.

Funnily enough I filed this ~13 years ago before I joined Microsoft, and it was "fixed" by restricting the user from putting an empty Default Namespace via the UI. ie This bug has always existed since Whidbey.

I'm not sure what the real fix is here - put a fake namespace? Don't generate a namespace for the class itself (which would require us to basically ship different templates just for the empty case)?

from templates.

We could write a wizard that removes the namespace text if the rootnamespace property is empty. UI-less template wizards can make arbitrary file modifications and read the dictionary of all template parameters. What does dotnet new do if you set the default namespace to nothing?

from templates.

You could probably hack it with the basic #if support, but then you'd also need to format the document afterword.

from templates.

In VS I it will auto-format the file on creation. Don't know if any of that works in the CLI templating engine

from templates.

Why not just fall back to the name of the project? That doesn't seem fake to me, considering the "default default" namespace is the project name.

from templates.

@SolderedMushroom Because the this isn't the case where the default namespace is set to the project name, this is the case where the default namespace is literally empty.

from templates.

@davkean Right, my point is just that since an empty namespace is invalid, falling back makes sense, and the project name is the "true" default (what you'd get if the default namespace isn't user-specified).

from templates.

The template should prevent this from happening

from templates.