Publish new version with removal of Newtonsoft.Json and upgrade to .NET 10.

[babaktaremi]

I noticed there are commits updating the .NET version, but no corresponding releases on NuGet. This is a great package that we use in several enterprise applications, so I was wondering—has the project been discontinued?

[XzaR90]

I hope not, I would like to have suppport to .net 10 and I can see there is commits replacing newtonsoft.json too

[RobSlgm]

I ran into these same issues and had a use case that the current library didn't support. To address this, I've created a fork with a complete re-implementation.

This version is designed for .NET 9+ and focuses on modern standards (RFC 8292, RFC 8188). I’ve also removed the dependencies on Newtonsoft.Json and BouncyCastle to keep it lightweight.

If anyone is looking for a modern alternative (with breaking changes), you can find it here: https://github.com/closureOSS/webpush-csharp or https://www.nuget.org/packages/ClosureOSS.WebPush

I'm happy to discuss a PR, though the changes are quite architectural given the .NET 9 requirement and drop of older standards.

[Nickztar]

I think a PR would be wasted here sadly. Your fork seems really good and I might try switching to it. Would be nice to contact the web-push-libs github organization and see if we can have a new maintaner?

[AnsonNHS]

Has anybody received a response yet? I've contacted @coryjthompson for a response.

[coryjthompson]

I will take a look at publishing these changes in the next few days, with an upgrade for .NET 10.

@RobSlgm I would be very happy to discuss a PR, your changes look great. I would like to maintain backwards compatibility but I can look at managing the backwards compatibility.

[RobSlgm]

@coryjthompson Thanks for the feedback. I plan to take a look at integrating my changes into the project over the next two to three weeks.

While I understand the importance of maintaining backwards compatibility, it would be helpful to clarify which legacy use cases we still need to support. For example, my understanding is that the GCM API key has largely been retired in favor of VAPID, and draft-ietf-webpush-encryption-09 has been superseded by RFC 8291.

Knowing if we want to move toward these modern standards or continue supporting the deprecated versions will help me structure the PR correctly.

[RobSlgm]

@coryjthompson I have analyzed the necessary changes to integrate https://github.com/closureOSS/webpush-csharp and identified a primary blocker: replacing Bouncy Castle requires System.Security.Cryptography.HKDF and other System.Security.Cryptography.* libraries, which are only available in .NET 8.0 or higher.

While I could revert newer C# features (like nullables and collection expressions) to maintain compatibility with older frameworks, the point is moot because HKDF is a hard requirement. Using #if preprocessor directives to support both encryption libraries would, in my opinion, make the codebase unmaintainable.

To move forward, I see either a Unified v2 Branch: We merge the changes into a new v2 branch in the original project, officially dropping support for .NET 4.8 and lower to allow for modern dependencies. Or we leave it as it is.

I'd love to hear your perspective on this.