There are other characters that can't appear in a file name (differs slightly depending on OS). I suggest to have a method in File (or later Path) to check if a string is a valid path component.

This SO answer looks quite comprehensive: https://stackoverflow.com/a/31976060/7401689

Also, instead of having a blacklist, we could go the other way and have a whitelist?
This is the project name, this name will be used (with some modifications) for the module name in the generated code

Thinking more about this, the whitelist solution will never be complete, as almost any unicode char is allowed in a module name (like A€あ).

So either:

• the tool only handles a subset of what's possible, by allowing only alphanumeric + dash & underscore
• we try to list all the unsupported chars (like >, :, /, {, }, ....) and test each of them to make sure the name is fully correct.

I don't see a reason to artificially restrict the usage of arbitrary unicode characters in file names. So it should only check against a blacklist of (potentially) invalid characters.

@straight-shoota Nice idea! We can add a list of invalid chars to File or later Path and have a method check if a string is valid.
dotnet has GetInvalidFileNameChars and GetInvalidPathChars, both for unix and windows.

Closing in favor of #8737
Thank you nevertheless @bew