Skip to content
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

Orleans GernerateSerializer breaks when Obsolete attribute is used #9311

Open
RundaScath opened this issue Feb 5, 2025 · 0 comments
Open

Comments

@RundaScath
Copy link

My team is currently working with Orleans v9.0.1 as a whole

We have a seperate repo we build our models in that uses the Microsoft.Orleans.Serialization.Abstractions nuget package version 8.2.0 which we are using the GenerateSerializerAttribute class as a class level decorator on our models. We are not seeing any issues building or packageing this repo into a nugt package our main Orleans repo consumes

In our main Orleans repo where we are building and defining our silos and grains we are using Orleans Nuget Packages version 9.0 or newer, except for OrleansDashboard which we are using verison 8.2.0 (though I dont htink its to blame)

Issue Being Seen:

When we build the main Orleans repo after consuming a nuget package of our modeling repo where an data dictionary object has an Obsolete decorator on at least one field we get a build failure with teh following message...

"CSC : error ORLEANS0101: Serializable property {Full Name of DataDictionary} does not have an accessible setter [{Full Path to the project file}]"

Troubleshooting Steps Taken:

  • Removing the Obsolete decorator fixed the build (but not what we want)
  • Updating all related pacakges to the latest versions (Orleans and System.Text.Json), however the build still failed for the same reason.
  • Looked into current and past issues on this repo...
    • Found a closed issue back in 2016-17 ish time fram that had a similar issue but was resolved
    • Found no open issues of similar concerns
  • Investigated the source code a bit and found a possbible point of interest to this issue

Unfortunitly my company does not allow me to use my company login to submit to third party repos which is why I am submitting this issue under my personal account. Please do let me know if there is more informaiton in regards to this you would like me to gather for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant