Here's the situation. I developed a Serializable class in one application, and then I binary serialize the info to a file. Using the exact same class in another one of my applications, I cannot deserialize because of some security measures in the .NET framework.
Here's the error I get when dezserializing in the other app:
China based gaming consultant Daniel Olimac says Black Myth Wukong releasing on Xbox exactly 1 year after the PS5 release has nothing to do with a Sony exclusivity deal “I know it has nothing to do with an exclusive agreement with Sony.
Game Science has been using August and the 20th for announcements since 2020.” “Indeed, it may seem like a big coincidence that it is one year after the launch on PS5, but that is exactly what it is: a coincidence. The date of August 20, 2024 was not random. It is a special date for the studio, and they continue to use it.”
Yes, I bought 8 of the 2025 models in various sizes for a reginal office I opened a few months ago. They work well for the price, and have surprisingly good built-in sound. I used the 85" model in a conference room, and the amp for the ceiling speakers ended up being on backorder, so I routed the conference audio to the TV. It not only worked, but the employees said they didn't even notice a difference (I did, but still very passable performance).
Question
Vorenus
Here's the situation. I developed a Serializable class in one application, and then I binary serialize the info to a file. Using the exact same class in another one of my applications, I cannot deserialize because of some security measures in the .NET framework.
Here's the error I get when dezserializing in the other app:
Where 'GDB Tester App' is the name of the app that was used for serialization.
How can I workaround these darn security measures?
Thanks in advance.
Link to comment
https://www.neowin.net/forum/topic/337144-c-binary-serialize-deserialize-in-another-app/Share on other sites
11 answers to this question
Recommended Posts