Post

Every time I do work in .NET these days, I curse the dotnet team for not supporting something like `--env-file=.env` natively on the dotnet CLI. They've built a massive system where you can get config from anywhere. Yet, they made sure to exclude the local dev setup that EVERYTHING ELSE SUPPORTS!

16/10/26, 5:37 pm0 reposts1 like

Jake Carpenter

@jakecarpenter.dev

And yes, there is a third-party NuGet package, but I'm on a team of .NET developers who don't do anything outside of .NET and neither understands nor trusts .env files. So, getting them to utilize them for local dev secrets is a non-starter. The team needs cohesion.

Kirill Osenkov

@kirillosenkov.com

@chethusk.bsky.social