Orleans 8.0 compatibility

[jaredthirsk]

AddRedisGrainStorage exception:

System.TypeLoadException: 'Could not load type 'Orleans.Runtime.KeyedServiceExtensions' from assembly 'Orleans.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null'.'

[hendrikdevloed]

I had the exact same error in my project.

My attempt at migration is in #44
Tests were run and are green.
In my Orleans application, a local .csproj was added instead of the Nuget package and now successfully works on NET8.

However, I have no experience contributing to the Orleans project nor how to update the Nuget bookkeeping. I bumped the package to 8.0.0 and SDK version to 8.0.100.
Please give me some hints or fork and add the missing parts to make this into a proper Nuget update to v8.

[scalalang2]

any update?

[ReubenBond]

If you create a PR, I will help with the release process

[FabianNet]

upgrade to .net 8 would be super ;)

[kzu]

I got this error too, and it was because bumping to Orleans 8.x (in my case) also required bumping the project to .net8. That fixed the issue.

[urumo]

Honestly this seems like a must have at this point in time. What exactly needs to be done to make this package compatible with Orleans 8 and .Net 8?

[code-maid]

You are seriously????
ZERO Support about this library
Why did you even take up this case if you are not able to provide proper support, why there are links to your repositories in the official documentation, I just can't understand.. can't understand
Why are you publishing under the Orleans prefix. and you're not doing your job.
Of course, I understand that this is also a question for Orleans dev, but I do not understand.....

[rkargMsft]

(I'm not on the Orleans team)
Microsoft.* packages are the ones that are maintained by Microsoft.

OrleansContrib are community contributions that are maintained by the community and not directly by Microsoft.

There's actually Redis support in the core Microsoft packages now which seems to have addressed the needs of other .NET 8+ users:
#44 (comment)
Does that work for your scenario? If there are any gaps then it would be good to get issues lodged against those implementations instead of trying to maintain two separate implementations.

Source: https://github.com/dotnet/orleans/tree/main/src/Redis
Example Package: https://www.nuget.org/packages/Microsoft.Orleans.Clustering.Redis

Perhaps the ReadMe for this repository should be updated to prominently call out that it's been replaced by the in-box packages?

[galvesribeiro]

You are seriously???? ZERO Support about this library Why did you even take up this case if you are not able to provide proper support, why there are links to your repositories in the official documentation, I just can't understand.. can't understand Why are you publishing under the Orleans prefix. and you're not doing your job. Of course, I understand that this is also a question for Orleans dev, but I do not understand.....

@code-maid please lets stop.

First of all, as any OSS project under the MIT license (like this one), there are no warranties, support or guarantees. The code is provided as is.

Secondly, as @rkargMsft just mentioned, this is not the main Orleans repository. This whole organization is about contrib projects. If you don't know what it mean, I would suggest you have a look on your favorite search engine but in a nutshell, it means that outside of the main project it relates to, the community makes extensions which are not maintained by the main repository and its contributors. Many projects from this organization eventually may or may not be integrated with the main repository (like many did) but there are no obligations.

The fact that the main documentation references this organization doesn't make it an official package on any matter. The fact it has the name Orleans also doesn't meant anything. It could be called "banana.Redis" and would be the same. It is just that people name the projects here as what it relates to.

That being said, it is always good to treat people (specially those that we are not paying for) in a healthy way.

The project is open source. The problem on this issue is cause by outdated packages. Literally ANYONE with a GitHub account can make a PR with the updated packages and the maintainers will consider and eventually provide feedback or merge it.

Contributions are always Wellcome.

[code-maid]

You are seriously???? ZERO Support about this library Why did you even take up this case if you are not able to provide proper support, why there are links to your repositories in the official documentation, I just can't understand.. can't understand Why are you publishing under the Orleans prefix. and you're not doing your job. Of course, I understand that this is also a question for Orleans dev, but I do not understand.....

@code-maid please lets stop.

First of all, as any OSS project under the MIT license (like this one), there are no warranties, support or guarantees. The code is provided as is.

Secondly, as @rkargMsft just mentioned, this is not the main Orleans repository. This whole organization is about contrib projects. If you don't know what it mean, I would suggest you have a look on your favorite search engine but in a nutshell, it means that outside of the main project it relates to, the community makes extensions which are not maintained by the main repository and its contributors. Many projects from this organization eventually may or may not be integrated with the main repository (like many did) but there are no obligations.

The fact that the main documentation references this organization doesn't make it an official package on any matter. The fact it has the name Orleans also doesn't meant anything. It could be called "banana.Redis" and would be the same. It is just that people name the projects here as what it relates to.

That being said, it is always good to treat people (specially those that we are not paying for) in a healthy way.

The project is open source. The problem on this issue is cause by outdated packages. Literally ANYONE with a GitHub account can make a PR with the updated packages and the maintainers will consider and eventually provide feedback or merge it.

Contributions are always Wellcome.

Thanks for the outrage!!!
I was misled by a package with the prefix Orleans.*
I apologize