Added event handler for MemoryManager operations.

[fjbelizon]

• Added event handler for MemoryManager operations.

[LuisM000]

We could simplify the code by sending the current instance of MemoryManager (i.e., 'this') as the sender when the event is raised. I notice that in most cases, the description of the generated event (MemoryStorageEventEnum.Upsert.GetEnumDescription()) is currently being sent as the sender. While I understand that there may be a specific reason for this, it's worth mentioning to ensure clarity :)

[rliberoff]

We could simplify the code by sending the current instance of MemoryManager (i.e., 'this') as the sender when the event is raised. I notice that in most cases, the description of the generated event (MemoryStorageEventEnum.Upsert.GetEnumDescription()) is currently being sent as the sender. While I understand that there may be a specific reason for this, it's worth mentioning to ensure clarity :)

Perhaps add comments in the code to explain how this event is expected to work and be consumed. For instance, that the name of the event is sent to allow handlers to filter.

[fjbelizon]

We could simplify the code by sending the current instance of MemoryManager (i.e., 'this') as the sender when the event is raised. I notice that in most cases, the description of the generated event (MemoryStorageEventEnum.Upsert.GetEnumDescription()) is currently being sent as the sender. While I understand that there may be a specific reason for this, it's worth mentioning to ensure clarity :)

There is no reason for this. Your arguments are logical and the event type is sent in the arguments, so it doesn't make sense to send the event type in the sender. I modify it to send the sender correctly.