-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible issues using the .NET 7.0 SDK for builds #582
Comments
Hey @daghsentinel thanks for reporting! Can you exclude that this is not happening with older versions? Do you have any cluster id you could share? |
@xlegalles do you experience similar issues? |
We are still using v2.0. I will upgrade and tell you. But just a quick note about the fact that v2.3 is built for .NET 6 and 7, not for .NET 8 i.e. if you open the Nuget package, there is no .NET 8 version, so it's not surprising that a .NET 8 app uses the zeebe client built for .NET 7. To be honest, I don't know what are the consequences and if there can be incompatibilities (because of Grpc for instance). Now, It's up to you @Zelldon to decide when to add a .NET 8 version as it's still a preview version. |
Hi, @Zelldon. I did a little concept of forking this repo, updating TargetFrameworks to include If that's not possible right now, I'll just keep my fork, use it in our apps and update to the official .NET 8 version as soon as it arrives. |
Thank you both @daghsentinel and @xlegalles for your input! Yeah based on what I can see here https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core and other resources I would prefer to only support it when it is officially released, so let's wait for November. I will keep this issue open so I can reference a PR in November for that. Feel free to create a PR then if you are interested. P.S: TIL; I somehow expected that the .net versions are backwards compatible and that you can run a .net7 lib with .net8, but seems not. Interesting. |
Thanks, @Zelldon. A thing to consider: When it comes to support, the versions of .NET (Core) officially supported by MS is now
The rest are either out of support or supported in the future, like .NET 8 full release) |
Describe the bug
We're experiencing "Deadline exceeded" for all communication after upgrading the client to 2.2.0 for our .NET 8.0 RC1/2 projects.
To Reproduce
Include client v2.2.0 in any project and try to create workflows, either on prem or in Camunda Cloud
Expected behavior
Command goes through
Enviroment (please complete the following information):
Additional context
Can the fact that the CI build is configured to use .NET 7.0 SDK be the real issue here? I notice that the CI workflow is persistently using .NET 7.0, also for .NET 8.0 builds.
The text was updated successfully, but these errors were encountered: