←back to thread

201 points olvy0 | 2 comments | | HN request time: 0.001s | source
Show context
zija ◴[] No.41882129[source]
I don't understand why the dotnet team doesn't invest more resources and time into tools: doctests and documentation generation, better and faster unit tests that I can write next to the actual code, easy access to the source code, no need to decompile a Dll to see it after pressing F12, a central place for packages and documentation like in pkg.go.dev or docs.rs . Most packages in nuget have no documentation at all, or only in readme format on GitHub, or a short Wiki on this page. Other environments like Rust, Golang, Java, Python are light years ahead when it comes to these aspects.
replies(5): >>41882271 #>>41882721 #>>41883613 #>>41883692 #>>41885066 #
Merad ◴[] No.41882721[source]
Sandcastle Helper File Builder has been around forever and started as an internal MS project IIRC, but for some reason few libraries use it.

https://github.com/EWSoftware/SHFB

replies(1): >>41883675 #
1. progmetaldev ◴[] No.41883675[source]
I used to use this quite a bit after it was introduced, but CHM files are a bit unwieldy for documentation, at least for myself. Having integrated search is nice, but the windowed interface, and being tied to Windows (AFAIK, maybe there are readers for other operating systems) I believe will keep this project from being used. I always found it to be decent for more advanced developers, but felt there was something missing for more junior developers that needed documentation.
replies(1): >>41885427 #
2. Merad ◴[] No.41885427[source]
I haven't used it in 4-5 years but at the time we were generating html docs with it. IIRC it supports several other output formats.