Meir Blachman

@ReubenBond I updated the description of this issue with a suggested plan for getting this done safely

@ReubenBond are we okay upgrading the sdk version?

the Command-line configuration provider https://learn.microsoft.com/en-us/dotnet/core/extensions/configuration-providers#command-line-configuration-provider almost matches the command-line arguments that exist today. I think the command-line arguments can wait (still use the Options class) but adding support for environment-variables...

@mmiscool try here https://github.com/node-projects/esprima-next

for sql-server I found the following way: ```cs var sqlServer = builder.AddSqlServer("sql-server") .WithDataVolume("data"); sqlServer.WithCommand("open-in-vscode", "Open in VS Code", async context => { var rawConnectionString = await sqlServer.Resource.GetConnectionStringAsync(); if (string.IsNullOrEmpty(rawConnectionString)) {...

see how deno does this https://jsr.io/docs/scoring

@bart-vmware is this still an issue?

Related to #550

@JeppeSN I think this is already supported by the Microsoft rolsyn analyzers (ex: https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-messages/cs4014?f1url=%3FappId%3Droslyn%26k%3Dk(CS4014) for example:  you can enforce this using `.editorconfig`

you can use https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD110.md Basically add https://www.nuget.org/packages/Microsoft.VisualStudio.Threading and then you will get diagnostics