To disable implicit restore, use the -no-restore option. You don't have to run dotnet restore because it's run implicitly by all commands that require a restore to occur, such as dotnet new, dotnet build, dotnet run, dotnet test, dotnet publish, and dotnet pack. Instead, create a deployment using the dotnet publish command and deploy the published output. Because it uses cached dependencies, it's not recommended to use dotnet run to run applications in production. To run the application, the dotnet run command resolves the dependencies of the application that are outside of the shared runtime from the NuGet cache. For example, to run myapp.dll, use: dotnet myapp.dllįor more information on the dotnet driver, see the. If you're trying to run a framework-dependent application DLL instead, you must use dotnet without a command. The dotnet run command is used in the context of projects, not built assemblies. If the project specifies multiple frameworks, executing dotnet run results in an error unless the -f|-framework option is used to specify the framework.
Temporary files are placed in the obj directory. For example if you have a netcoreapp2.1 application and you run dotnet run, the output is placed in bin/Debug/netcoreapp2.1.
Output files are written into the default location, which is bin//. Dotnet run doesn't respect arguments like /property:property=value, which are respected by dotnet build.
0 kommentar(er)
