-
Notifications
You must be signed in to change notification settings - Fork 29
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
ulong enum #219
Comments
Thanks for the details. I can look into the code to see what causes it. Thanks |
My fault, I forgot to mention that it is a Flag-Enum. Sorry :(
So that will result in issue 1, but unfortunately not in mystic issue 2... |
I see. Thanks for the details |
Regarding my second problem, I was now able to reproduce the problem. It occurs when a long or ulong enum is used. However, exclusively out of a uwp project. Your example code within a UWP project then generates the following message. Unfortunately there is almost no further info. Looks like a bug in the platform. :( |
The problem is in the flagenumToStr method that try to cast to int and check for zero as an optimization. If you remove that then it works fine. But I found a weird bug when in release mode that give junk data when a single value is used as the enum from the flag. Trying to figure out the cause of it. |
One question not related to my problem: If I serialize an interface type, why are properties of the base interface ignored? |
Can I see an example of what you are trying to do? Thanks |
|
So the interface will not get the other properties since it does not exists. It only exists in the class itself. You need to enable NetJson.IncludeTypeInformation = true and try again |
Please verify if the changes i did solves your problem by using the code from the branch. If so, i can create a nuget package for it. In regards to the enumeration ulong. Please a separate ticket to discuss the serialization of Interface Thanks, |
The first problem FlagEnumToString is solved, thanks! :) |
Hey there,
I have found two issues:
It happens when CreateSerializer() is called on the last Emit call. (Maybe this is nocht the actual line, because it was a dotpeak decompiled assembly and this is sometime not exactly at the right line, could be one more maybe).
However, there is not any more information I get or can provide. Maybe you have any idea or hint what could cause this or how to make a further diagnosis?
Thank!
The text was updated successfully, but these errors were encountered: