Inside the published folder, we can run our app by running the executable file: We can quickly go to the published folder by clicking on a path inside Output Window. When using Release Configuration: \bin\Release\netcoreapp3.1\publish.We can also choose to publish as a single file.Īfter publishing is completed using Folder publishing method, the built files will be located inside the publish folder depending on the Configuration setting: Here we can choose to erase the content of the publish folder before publishing.
Note that with Portable, you get binaries for other platforms too (for example. NET Core runtime already installed.įor Target Runtime, we can choose Portable or Platform specific. Framework-Dependent on the other hand is a type of deployment in which the app will run on a machine with. NET Core runtime files installed, but it will also add additional 90MB in size with the. NET Core runtime files, so it's useful for systems that might not have. Using Self-Contained, the published folder will also include the.
Here we can choose between Framework-Dependent and Self-Contained. By clicking on the edit icon located near those settings, we get a new window where we configure the settings to our needs.
0 kommentar(er)
