#xmlresolver — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #xmlresolver, aggregated by home.social.
-
At the intersection of pain and suffering. There are Unix filesystems and Windows filesystems. There are Java URI objects and C# URI objects. There are file: URIs. And they all intersect in the XML Resolver. #XMLResolver #MarkupMonday
-
XML Resolver version 6.0.23. Closing in on 6.1, this release exercises the new build infrastructure, mitigates a couple of Microsoft CVEs in the C# resolver, and adds support for “new” HTTP status codes in the Java resolver. #XML #XMLResolver #Java #MarkupMonday
-
XML Resolver 6.0.{last}?. Is it ready yet? #XML #XMLResolver #Java #CSharp #MarkupMonday
-
XML Resolver updates. I’ve pushed an update for the XML Resolver, 6.0.13, and a patch on the legacy V5 branch, 5.3.0, to address a security vulnerability. #XML #XMLResolver #Java
-
XmlResolver for .NET updated. This is a feature-free update that (mostly) just nudges the dependencies forward. I believe it also supports either .NET6 or .NET8. #XML #CSharp #XMLResolver
-
XML Resolver 6.0.11. Still pushing forward. Small fixes and one new feature. #XML #XMLResolver #Java
-
XML Resolver 6.0.8. Getting closer to a pushing 6.1.0 as a no-longer-in-beta version of the XML Resolver. #XML #XMLResolver #Java
-
Ring any bells?. When Xerces resolves a URI on Windows, it does it…differently than on Linux and MacOS. And incorrectly. #XMLResolver #Windows