HTTP Dot Net Core 2.2 Error 500.30 - ANCM In-Process Start Failure

When developing in .Net Core 2.2 sometimes when there is a configuration error, the debugger fails to attach to the Server process.

 

Please Login to see the rest of the answer
Answer:
  1. Check in the appsettings.json of anything that you added, normally if there is an error, you will see a squiggly line on it. 
    - Best practice, code in chunks and see if it breaks anything. I mean to write one line of code and check if it passes or no errors happen. Normally this is how development is done when you are learning a new technology on the block.
  2. This might be due to the mix of libraries from other versions of .Net Core e.g. If you attempted to upgrade ASP.Net Core 2.2 to version 3.1 all library dependencies are supposed to be upgraded as well.
  3. Make sure that you do not have any duplicates of dependencies in the Dependency Injection Container in startup.cs.
  4. Visit this link here to Microsoft troubleshoot page for known errors 

 


Write an Article
If you log in, you will be notified when someone leaves a comment.

Other users would like to know if this solution helped you.

John said:

Thank you.


© 2022 - ErnesTech - Privacy