To deploy the application manually, the dotnet command-line tool offers the publish command. In a nutshell, what it does is pack everything together, get all of the required dependencies from the project file, build the application and any dependent projects, and then copy all output to a target folder. It offers lots of options, but the most usual ones are probably the following:
hey are running from the user interface. Let's see how:
- -c | --configuration: This defines the build configuration. The default value is Debug and the other common option is Release, but of course, you can create other Visual Studio profiles.
- -r | --runtime: This publishes the application for a given runtime, in the case of self-contained deployments; the default is to use whatever runtime is available on the target machine. See the description in the Self-contained deployments and runtimes section.
- -f | --framework...
