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

Variable output depending on the runtime version used #23

Closed
Dypso opened this issue May 3, 2022 · 4 comments
Closed

Variable output depending on the runtime version used #23

Dypso opened this issue May 3, 2022 · 4 comments

Comments

@Dypso
Copy link

Dypso commented May 3, 2022

I am doing some test serializing an object from a client application build in .Net Core 6 framework and calling a server application running in .Net Framework 4.8 and Ihave observed that the same object is not serialized in the same manner under the two frameworks.
Is that a normal behavior ? Do we need to always serialize and deserialize with the same .Net framework or core version ?
Anoter point, is that my client application is a 64bit process while the server application is a 32 bit process : may be the issue is more related to this point...

@Dypso
Copy link
Author

Dypso commented May 4, 2022

After doing some more test, I have found that the problem is effectively come from the using of twodifferent runtimes : if we serialize from a process in .Net Core 6 , we would not deserialize from a process targeting the 4.8 Framework .Net runtime...

@salarcode
Copy link
Owner

Sorry for the late reply, I'm a little busy.
The binary is compatible with different version of .Net runtimes.
Can you provide an example of this incompatibility? A working dto class that has this issue.

@salarcode
Copy link
Owner

I have tested this and the output is same for the same model class

@Dypso
Copy link
Author

Dypso commented May 19, 2022

Yes sorry, I have done some more tests and it appears that the error was all mine. My bad. Really sorry.

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

2 participants