Golam Kibria's List: dotNET/etc

• An event is a message sent by an object to signal the occurrence of an action.
• The event is typically a member of the event sende

• Starting with the .NET Framework 4, you can use in-process side-by-side hosting to run multiple versions of the CLR in a single process
• The .NET Framework 4.5 is an in-place update that replaces the .NET Framework 4 on your computer.

• Each of these items is called, individually, a symbol

• memory management rules can be summarized (somewhat simplified) like this:
• If you create an instance of a class, you are responsible for releasing/freeing/disposing it.
• If a factory creates an instance of a class, the factory is not responsible for releasing/freeing/disposing it. This burden falls upon the object which requested the object from the factory
• If you receive an instance of an object, you should not release/free/dispose it, unless you received the instance from a factory
• This entire problem has been described as the Component Burden by Hammet, the original creator of the Windsor IoC container
• the container would keep track of all of the disposable dependencies it has created to satisfy the creation of requested components. Then when the requested component would be released, the container could safely dispose of each transient disposable dependency it created to create the requested component

4 more annotations...