Closed Richard-Payne closed 4 years ago
We use it at Redgate to document our binary cmdlets in various products, which it does just fine. Essentially, it's mature enough for our purposes, and whilst it is being maintained, it's not really being actively developed in terms of new features. The most likely upcoming change will be to get it to work under .NET Standard, and to make sure the integration with MSBuild and the new VS2017 file format works.
If there's anything you think it should be doing but isn't, or something that's not working correctly, please do let us know.
ok, cool. The only comment I had was that when you turn on the option to force a build failure, the error message is very unclear with no link to the problem doc comment. You have go through the build logs to find the "warning" message.
Ah, #30 is an enhancement request for that. This might just give me enough of a kick to have a stab at some of the outstanding issues here. I may well have a bit of free time me this coming weekend, so maybe it's time to crack open this codebase again. :)
Yeah, I saw that. That was the reason I asked if it was being maintained. I'm surprised you're active using it with the current reporting. Maybe you're just better at writing the comments right the first time. ;)
There's been little activity this year. Is this project still being maintained?