Why is Initialize not called from OnDeserializedHandler?

According to the code comment, Csla.Core.Initialize "allows subclass to initialize events before any other activity occurs". It is called from the constructor of BusinessBase, before any initialization of business rules or authorization rules. However, it is not called on deserialize of the object. Why is this?

You should override OnDeserialized() to do any event rehooking and so forth.

I understand that, but don't understand what the point of Initialize is in that case.

Implementing OnDeserliazed for the same functionality as Initialize is inconsistent: Initialize runs _before_ CSLA's initialization on constructor, but OnDeserialized runs _after_ CSLA's initialization. There is no way to run initialization logic _before_ OnDeserialized.

If I need to override OnDeserialized anyways, why not simply implement the custom event hooking in the constructor of the descendant class, in order to keep the timing consistent?

Semantically they aren't necessarily the same.

Initialize() exists so you can initialize elements of your object when it is
first created.

OnDeserialized() exists so you can reset elements of your object after it
has been deserialized.

Some elements of your object may need initialization only. Others may need
to be reset on deserialization only. Others may need both.

So I don't necessarily disagree with the concept of an "OnDeserializing()"
method - though it would still technically run after deserialization is
complete (because we don't control that - deserialization is purely a .NET
thing). But this is still not the same semantic operation as initializing a
new object instance.

What is your scenario where you need to reset elements of your object after
deserialization, but before CSLA restores values like the Parent property,
etc?

Rocky