Make `dotnet run file.cs` compiled program location user-configurable

[orthoxerox]

Is your feature request related to a problem? Please describe.

Many enterprises have software restriction policies on their computers that block locations inside %USERPROFILE% and %TEMP% to defend against malware. Any local development is restricted to a specific work folder.
Right now, dotnet run uses %TEMP% on Windows: https://github.com/dotnet/sdk/blob/main/src/Cli/dotnet/Commands/Run/VirtualProjectBuildingCommand.cs#L452 and would fail on a machine with such a group policy.

Describe the solution you'd like

Please provide a way to configure the path dotnet run uses. Ideally it should be an environment variable (e.g., DOTNET_RUN_ARTIFACTS_PATH) to avoid typing an extra parameter every time.

[DamianEdwards]

I think this is already possible by configuring artifacts output. Implicit build files such as Directory.Build.props are supported by file-based apps and dotnet run app.cs so the output will go in the location specified by artifacts output instead of the temp location.

Is that enough to satisfy your request?

[jjonescz]

Adding #:property ArtifactsPath some/path should work as well.