The Generate nfig option can be disabled for heavy customizations. When possible, customizations you make to this file are also preserved. Rider will create this file using a template that ships with IIS Express. To launch IIS Express with our ASP.NET Core application, a configuration file is needed under. Usually, there will be no need to edit any of these – but just in case, let’s explain these three new options. NET Core launchSettings.json to run/debug apps in Rider for more tips and background on using launch profiles.įor IIS Express run configurations, Rider gives us a few additional configuration options: To change any other options, you’ll need to edit the launchSettings.json file. As with other launchSettings.json-based run configurations, we can specify the target framework and additional runtime arguments. Do read on if you would like to learn more – we’ll cover some details and additional configuration options that are available.įrom the toolbar (or the Run | Edit Configurations… menu), we can look at the configuration that Rider generated based on the launch profiles defined in launchSettings.json. Oh, and we also check whether a trusted developer SSL certificate has been set up, and allow generating a self-signed certificate in case it isn’t.Īfter creating a new ASP.NET Core project or loading an existing one that has a launchSettings.json file with an IIS Express profile, Rider auto-imports it as a Run configuration. We’ve added a settings page to help verify IIS Express is installed, including prerequisites. Let’s cut to the chase: the latest Rider 2019.1 EAP build supports running ASP.NET Core apps in IIS Express! There’s launchSettings.json support for IIS Express.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |