So when Unity reloads assemblies, the serialization process comes in to store data on the native side of unity to restore it back once the assemblies get reloaded.
But, will the data in DLLs get wiped out, too? Basically, are the DLLs reloaded, too, even if they did not change and theoretically wouldn't need to be recompiled?
I have some very hard to serialize data (delegates, possibly anonymous) and I have the possibility to embed the editor-side code into a DLL, if that helps me in any way around the serialization problem.
The background: I'm working on an action-based Undo system integrated into the default Undo system, using reflection of course. It works really nice now, but the problem I'm encountering is that all the data storing the custom action-based undo records get's wiped out. This HAS to be avoided at any cost to match unity's default behaviour obviously.
I just thought if it is possible by using a DLL or, if it is the only solution (if at all) a native library.
Thanks!
↧