Open azborgonovo opened 1 year ago
There is a workaround/containment that can be used locally (at least for setting up env variables).
Set the environment with the launchprofile instead of via --environment parameter:
dotnet run --launch-profile Staging -- db-patch file.sql
That workaround unfortunately does not work for me. I receive the same "is already constructed" as above.
Symptom
Running a command like
dotnet run -- db-patch file.sql --environment Staging
results in the following error:Context
I tried to set up my .NET 6 web application as described in the docs. In summary, my Program.cs file looks like the following:
My development environment is a macOS with Apple silicon.