Trying to use a MS sample code for Azure Ad/OpenID, I received this error when changing the version of .Net Core to 3.1. Looking through #6111, I could not find any solutions. I deleted the .vs folder thinking that the IIS Express .config file just needed to be recreated correctly for the new version because of the new InProcess module, still nothing. Then I ran across some post on asp.net site about someone having this issue and found that it was caused because of a space in the project name. I tested if that was the issue, and it seemed to fix it. Even though I had no spaces. I rename the project from WebApp-OpenIDConnect-DotNet to just simply WebApp, low and behold it started as expected. There seems to be an issue with the length of the assembly name, as I renamed it back and changed the assembly name to be WebApp, and it successfully started again. To rule out file path being to long, I moved the project to the root of the drive and left the assembly name long, same error.
Trying to use a MS sample code for Azure Ad/OpenID, I received this error when changing the version of .Net Core to 3.1. Looking through #6111, I could not find any solutions. I deleted the .vs folder thinking that the IIS Express .config file just needed to be recreated correctly for the new version because of the new InProcess module, still nothing. Then I ran across some post on asp.net site about someone having this issue and found that it was caused because of a space in the project name. I tested if that was the issue, and it seemed to fix it. Even though I had no spaces. I rename the project from
WebApp-OpenIDConnect-DotNet
to just simplyWebApp
, low and behold it started as expected. There seems to be an issue with the length of the assembly name, as I renamed it back and changed the assembly name to beWebApp
, and it successfully started again. To rule out file path being to long, I moved the project to the root of the drive and left the assembly name long, same error.