Framework-Dependent Deployments

The default deployment model that Visual Studio configures for a .NET Core application is the Framework-Dependent Deployment model. Here, when you publish an app, only the portable, executable DLL will get generated, which you need to run in a system where .NET Core is already installed.

To publish an app to create the deployment package, right-click on the project and, from the context menu that pops up on the screen, click Publish..., as shown in the following screenshot:

This will open the publishing wizard dialog on the screen. For a console app, the publishing target is File System. If you are publishing a web application, you can publish it to Azure App Service, Azure Virtual Machine, IIS, or FTP along with the File System:

Click on the Browse... button to select the publish folder (the default is binReleasePublishOutput) and, when you are ready, click on the Publish button. This will publish the app to the selected folder and show you a summary:

In the summary section, you can see that the build configuration is Release and the target runtime is Portable. Click on the link labeled Settings, which will open the following Profile Settings page:

On this screen, you will be able to change the configuration, target framework, and target location. As we are publishing it as Portable Executable format (FDD model), you won't be able to change the target runtime.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.145.191.169