JSON deserialization of grain states does not bind GrainReferences to runtime about orleans.redis

[ReubenBond]

uhoh, thanks for pointing this out @heikki-heikkinen-ptcs. Are you able to submit a PR? We can make a quick release afterwards.

[heikki-heikkinen-ptcs]

@ReubenBond Sure, I'll cook this up on my pipe vision breaks. BTW are there any agreed practices for fixing code style, beautification and unrelated issues? There are some that are not directly related.
Examples:

• private const string _writeScript: This might be a naming convention issue depending on what they are. Commonly const fields are in PascalCase.
• Structured logging issue:

var initMsg = string.Format("Init: Name={0} ServiceId={1} DatabaseNumber={2} UseJson={3} DeleteOnClear={4}",
                            _name, _serviceId, _options.DatabaseNumber, _options.UseJson, _options.DeleteOnClear);
_logger.LogDebug($"RedisGrainStorage {_name} is initializing: {initMsg}"); 

In this case there are several issues:

• _logger.LogDebug: call takes an interpolated string as a parameter. This should be exploded into a structured logging call where the format arguments are passed to the LogDebug call as parameters

• The initMsg should not be passed as a single parameter but should be incorporated as part of the entire log message using structured logging.

• If there is a good reason for adding the initMsg as a single log parameter the string should probably be formed wwith FormattableString.Invariant($"message goes here as interpolated string")

• Uninformative exceptions:

                    var etagEntry = hashEntries.Single(e => e.Name == "etag");
                    var valueEntry = hashEntries.Single(e => e.Name == "data");

• Sure the Single extension method is handy but it results in an uninformative InvalidOperationException with a generic message "Sequence contains more than one matching element" which doesn't tell you anything about the context.

Should I tidy things up or just do the bare minimum here?

[heikki-heikkinen-ptcs]

Pushed the rename to global.json to the PR by mistake. It was only preventing the solution from loading as far as I know if you don't have that exact version of dotnet SDK installed.
#11

[ReubenBond]

Fixed by #11