News for hackers. Stuff that matters.
Re:The Case for C# and .NET by JamesBarney on Monday July 25, 2022 @03:11AM (#32221404)
I think for swagger documentation you install the swashbuckle nuget package and then add these three lines

services.AddSwaggerGen();

app.UseSwagger();

app.UseSwaggerUI();

Re:The Case for C# and .NET by orthoxerox on Monday July 25, 2022 @06:04AM (#32222453)
ASP.NET configuration is one of the most arcane parts of .NET that I don't like. You have to perform the incantation thrice: add package reference, add service reference, invoke the builder extension. And there's the right order and the wrong order of invocations, and if you pick the wrong one, your app silently won't work correctly.
Re:The Case for C# and .NET by metaltyphoon on Monday July 25, 2022 @08:44AM (#32223541)
Arcane? What did you expect? Add a package and magically everything works? If you make it work by just adding a reference its “too much magic”, if you make it so people write everything “it’s boilerplate” and if you do something in between “its arcane”.
Re:The Case for C# and .NET by silon42 on Monday July 25, 2022 @04:31AM (#32221860)
Personally, I'd rather generate documentation at compile time.
Re:The Case for C# and .NET by piaste on Monday July 25, 2022 @05:31AM (#32222258)
I do it during tests.

Since I'm already spawning a TestHost and trying out various API calls, one of these tests basically does "curl $host/openapi/openapi.json | diff ./docs/openapi.json". If it spots a change and fails the test, I check that the difference is expected, and if so I temporarily enable and run a different "test" which actually writes the updated file.

Re:The Case for C# and .NET by wizofaus on Monday July 25, 2022 @05:01AM (#32222078)
Which you can do, by adding a post build step.