XmlResolver for .NET updated
Published by This is a feature-free update that (mostly) just nudges the dependencies forward. I believe it also supports either .NET6 or .NET8.
What happened was thpe1000 reported a vulnerability in the .NET version of XmlResolver. It wasn’t in my code, but one of the dependencies. (I’d say that third party libraries are a real pain except that I’m not sure I could survive the irony of making that statement in a post about a, uh, third party library.)
To pour salt in my wounds, I discovered that the dependency was, in fact, unused. It might have been needed at one point, but it wasn’t anymore. So I just removed it. As the saying goes, there are no bugs in deleted code.
Let’s call it a learning experience: check your dependencies.
While I was in the neighborhood, I decided to pull all the (remaining) dependencies forward as far as I could in .NET 8. And to learn how to publish a library that can be used with both .NET 6 and .NET 8. I think I did that.
I published updates for both the legacy V2 API (2.1.1) and the still-under-development new V6 API (6.0.3).
Please report bugs if you find ‘em.