search

KevinDockx / HttpCacheHeaders

ASP.NET Core middleware that adds HttpCache headers to responses (Cache-Control, Expires, ETag, Last-Modified), and implements cache expiration & validation models
MIT License
271 stars 57 forks source link

Update all out-of-date NuGet packages #117

Closed SeanFarrow closed 1 year ago

SeanFarrow commented 1 year ago

For v78 we should ideally update all out-of-date NuGet packages.

I'm happy to take this as it isn't that much work.

Ideally though, long-term we should use something like Dependabot to keep packages up-to-date.

KevinDockx commented 1 year ago

As long as it doesn't result in being unable to support .NET versions we still want to support, this is fine by me. Thanks Sean, you're doing a lot of work on this, it's much appreciated!

SeanFarrow commented 1 year ago

My view is we should support everything that is current? I.e, .Net 6+. If you agree, can you assign me to this please? Thanks, Sean.

From: Kevin Dockx @.> Sent: Wednesday, May 31, 2023 8:30 PM To: KevinDockx/HttpCacheHeaders @.> Cc: Sean Farrow @.>; Author @.> Subject: Re: [KevinDockx/HttpCacheHeaders] Update all out-of-date NuGet packages (Issue #117)

As long as it doesn't result in being unable to support .NET versions we still want to support, this is fine by me. Thanks Sean, you're doing a lot of work on this, it's much appreciated!

— Reply to this email directly, view it on GitHubhttps://github.com/KevinDockx/HttpCacheHeaders/issues/117#issuecomment-1570819577, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AALDK7TV64CSHSO4IDODYPLXI6L4DANCNFSM6AAAAAAYRHKDLM. You are receiving this because you authored the thread.Message ID: @.***>

SeanFarrow commented 1 year ago

Do we want to use .net 6 or 7 as the major version for packages?

KevinDockx commented 1 year ago

I'd go for the latest LTS version, so: .NET 6.

SeanFarrow commented 1 year ago

I'm thinking we should multi-target this properly and use .net 7 packages for the .Net 7.0 target and .Net 6 packages for the .Net 6 target.

We shouldn't have any issues with this as we are not really using anything that differs in either functionality or method signatures.

KevinDockx commented 1 year ago

Good point - that's a better idea :-)