Set a few breakpoints, step through code, and investigate in-memory values.ĭevelopers moving to Rider will have an equivalent experience with IIS Express. We can choose to run either configuration using Visual Studio's run button.įrom here, the running and debugging experience is what most developers would expect. One entry defines the IIS Express run configuration and its settings, and the other establishes the run configuration for ASP.NET Core running within the Kestrel server. Here we can see the run configurations for our web application. Visual Studio will read the launchSettings.json found under the Properties folder. Beginning with a new ASP.NET Core web application, we can see our solution structure, which includes C# files, JSON setting files, and launch settings.
Let's start with the more common IIS Express experience from Visual Studio, and how it compares to Rider's experience. Visual Studio users are familiar with hitting the play button and having everything "just work". The building, running, and debugging of web applications are necessary components of the ASP.NET development lifecycle. IIS comes in two different variants, IIS and IIS Express, with the latter being the most commonly used by developers in their daily work. For developers working with ASP.NET and ASP.NET Core, Internet Information Services (IIS) is an essential part of the web development workflow.
0 kommentar(er)
