Repository navigation
Infrastructure work items #1259
Description
Activity
- Migrate the documentation from using sandcastle to docfx
Added support for GitHub pages using docfx #1358
Relates to CHM file not in Asset list on lastest release. #1249 - Integrate with Nerdbank.GitVersioning Integrate with Nerdbank.GitVersioning #1299
- Generate symbol package to support source link
- Migrate the documentation from using sandcastle to docfx
- Drop support for
net462andnetstandard2.0(and maybe evennetstarndard2.1)
There are code improvements I would like to make but are much more challenging to do when having to support these legacy runtimes/standards. Anyone who wishes to use those runtimes stays on the
2023.xversion.- Drop support for
Long term that is the plan, but right now there is still plenty of scope for modernisation and bug fixes with the current targets. The library has only just dropped support for silverlight 😉
I won't argue the point, but for me there is no harm in freezing those older runtimes at this version. If additional bug fixes or security items are found, then we simply support those on a
releases/2023.xbranch. I'm personally feeling the pain of these old frameworks as I work on "async all the way down" and modern logging implementations, both of which get significant enhancements in later versions of the runtimes and are requiring a lot of conditional compilation to make them work.Please consider it, as I said, I don't see a downside to doing that, and it is directly impacting the modernization efforts.
P.S. - I'll only recently took an interest in contributing to this project, so you are free to ignore anything I say. 😁
If additional bug fixes or security items are found, then we simply support those on a releases/2023.x branch
IMO this is too much effort on behalf of the (not even a) handful of contributors.
"Async all the way down" is already possible with the current targets (I have been thinking about it lately). A few conditional directives are no problem.
Sure, keeping these targets makes some shiny features prohibitive, but (IMHO) there is much more work that should take priority.
It will surely happen one day, but given the current position of the library, I do see the downsides and very few upsides.
You are of course free to modify your own fork as you please.
P.S. - I'll only recently took an interest in contributing to this project, so you are free to ignore anything I say. 😁
Your interest is welcome :) As I said, there is lots of work to choose from
Let's discuss and coordinate ideas here to avoid crossing or unnecessary work. Feel free to add to (or remove from) the list.