Visual Studio 2019 creates invalid assembly name

This issue has been moved from a ticket on Developer Community.

---

[severity:I’m somewhat annoyed. A fix would be nice] I tried to create a ASP.NET Core 3.1 Web App using the following project/solution name: “Can’tDebugFF”.

Visual Studio apparently doesn’t escape the project’s assembly name.

The linker, too, doesn’t complain about the illegal assembly name.

Debugging the web app then results in:

FileLoadException: The given assembly name or codebase was invalid. (0x80131047)

System.Reflection.AssemblyName.nInit()

Please fix by correctly escaping assembly name on project creation.

---

Original Comments

Feedback Bot on 8/27/2020, 08:13 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

---

Original Solutions

(no solutions)

[Pilchie]

Note - as a workaround, it’s already possible to specify <AssemblyName>Can_tDebugFF</AssemblyName> in the project file.

[vlada-shubina]

The issue in developer community is already closed, and leads to this item. As we cannot reproduce it now, decision is to close it. Please don’t hesitate to reopen if needed.