Fix RedisCache update that breaks usage against older redis servers

[Tratcher]

Fix RedisCache update that breaks usage against older redis servers

Add version checks and alternate API calls to support older redis versions

Description

6.0 changed from calling a deprecated redis API to a new one. Unfortunately the new API doesn't work on unsupported versions of redis which are still in common use.

Fixes #38715

Customer Impact

Unblocks customers stuck using old versions of redis.

Regression?

• Yes
• No

In 6.0

Risk

• High
• Medium
• Low

Restoring the prior behavior

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

[ghost]

Hi @Tratcher. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document.
Otherwise, please add tell-mode label.

[ghost]

Hi @Tratcher. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge.

To learn more about how to prepare a servicing PR click here.

[NickCraver]

Not sure mine counts but backport looks good 👍

[Tratcher]

@dotnet/aspnet-build please merge.

[Joseph-Anthony-King]

Hello team, I'm currently working on a .NET6 project using the latest versions of StackExchange.Redis and Redis Server 6.2.6 and I'm receiving the following error:

ERR Error running script (call to f_3915ee22fda531a1d5661f2523d0443fd35ff0a4): @user_script:2: @user_script: 2: Wrong number of args calling Redis command From Lua script

I believe this change is meant to address this issue and I see it's merged... is a release pending?

Thank you,
Joe

[ghost]

Hi @Joseph-Anthony-King. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.

[dougbu]

@Joseph-Anthony-King yes, the 6.0.2 release contains this fix and should be available soon. Please watch for announcements or check https://dotnet.microsoft.com/en-us/download/dotnet/6.0 occasionally.

[Joseph-Anthony-King]

Very cool, thank you for the update @dougbu !

[ghost]

Hi @Joseph-Anthony-King. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.