STARTUP CONFIG IS NOT PRESENT CODE
STARTUP CONFIG IS NOT PRESENT WINDOWS

Copy the following configuration to NVRAM.

Why does this message appear No startup configuration present d. The switch responds with: Non-volatile configuration memory is not present c. I was trying to confirm that the file was definitely being loaded correctly, and the setting wasn't coming from somewhere else when running locally. To see the contents of the startup configuration file, type the show startup-config command in privileged EXEC mode as follows: Switchshow startup-config b. I tried debugging locally, adding and removing the file, and changing the setting value. In the next section, I'll briefly describe some of the things I thought of and looked into. For example, in Startup.Configure(), it's common to configure your middleware pipeline differently if you're running in 'Development' as opposed to 'Production': public void Configure ( IApplicationBuilder app, IHostingEnvironment env ) Д«ut for some reason, when the application was running in Docker for the smoke tests, the value wasn't being bound correctly. You can determine the current environment at runtime, and use the value to change the behaviour of your app somehow.

STARTUP CONFIG IS NOT PRESENT CODE

ASP.NET Core environmentsДЄSP.NET Core has the concept of environments, which represent the different locations your code might be running. Setting the environment to 'development' instead of 'Development' will result in your configuration files not loading on a case-sensitive OS like Linux. However, if you are using environment-specific configuration files, for example, then you must pay attention to case. Tl dr IHostingEnvironment ignores the case of the current environment when you use the IsDevelopment() extension methods etc. If you just want to see the bug, feel fee to skip ahead. Finally, I'll describe the bug that I ran into and why it was an issue. In this post I'll cover the basic background of environments in ASP.NET Core, and describe how you would typically use environment-specific configuration. I spent a good half an hour trying to figure out the issue, so this post is just in case someone else runs into the same problem! But when I pushed it to the build server, the application would immediately fail, citing a 'missing connection string' or something similar.

STARTUP CONFIG IS NOT PRESENT WINDOWS

The application would start up without any problems when running locally on my Windows machine. I was recently standing up a new ASP.NET Core application running in Docker, and I was seeing some very strange behaviour.

Startup config is not present