When a window is visible on the screen it undergoes various stages such as CreateWindow, ShowWindow, etc. Once the window is displayed on the screen it must now make itself ready to take keyboard and mouse input from the user. Windows maintains a message queue for each windows program currently running under windows. When an input occurs, the OS translates this event into a message that it places into the windows message queue. A program receives messages from the message queue by executing a block of code known as the message loop.  While (GetMessage(&msg, NULL, 0, 0)){            TranslateMessage(&msg);            DispatchMessage(&msg);}  The GetMessage call passes to windows a pointer to the message and these fields of the message are filled by windows.  The TranslateMessage call passes the msg structure back to windows for some keyboard translation. The DispatchMessage call passes the message to windows which sends the message to appropriate windows procedure for processing the message. So this means that windows call the window procedure

COM is an acronym for Component Object Model. COM is a way of building objects that is independent of any programming language.  Every COM object implements an interface named IUnknown. It contains three methods: -         QueryInterface: Returns a pointer to another interface -         AddRef:  Increments the objects reference count -         Release: Decrements the objects reference count. One of the rules of COM says that given a pointer to an interface a client can call any IUnknown method through that pointer as well as any methods that are specific to that interface. Hence all interfaces must support the three IUnknown methods in addition to their own methods.

Object Linking and Embedding (OLE) clipboard is a more capable clipboard than the windows traditional clipboard. To transfer a large image using a legacy clipboard one must allocate enough memory space to copy this image. However using the OLE clipboard you can transfer the bitmap in a more sensible medium like a file on a hard disk.OLE drag and drop is a visual method of transferring data. Unlike having separate commands like cut, copy and paste the OLE drag and drop lets you grab a piece of data with the mouse and drop it in the desired location.So to summarize it there are two broad differences between OLE and legacy clipboard. OLE clipboard is completely COM based and secondly it supports storage medium other than global memory.OLE drag and drop is programmatically very similar to OLE clipboard. The data provider or data source creates a data object that encapsulates the data and makes an IDataObject pointer available. The data consumer or drop target retrieves the IDataObject and uses it to extract data from the data object. The drop source initiates a drag and drop operation by passing an IDataObject pointer to ::DoDragDrop. Any window that is interested inbeing a drop target registers itself with the system by calling ::RegisterDragDrop. If drop occurs in a registered window then the drop target is handed the IDataObject pointer passed to ::DoDragDrop.

The concept of namespaces plays a very crucial role in .net framework. It is a concept parallel to the concept of packages in java. In general, a namespace is a logical grouping of types for the purpose of identification. e.g. let's say in an organization there are three people with name Paul Smith each individual in a different role and responsibilities. To resolve this ambiguity we can define three namespaces based on their roles as Secretary, Manager and Operator and then reference each Paul as Secretary.Paul and Manager.Paul and Operator.Paul. This is the concept of namespace.

Yes I have certainly worked on ADO.Net. ADO.net encompasses two groups of classes: content components and managed provider components. The content components include DataSet class and other supporting classes as DataTable, DataRow, DataColumn and DataRelation. The DataSet class is a lightweight cache of a particular database from the data store.  It allows reading and writing of data and schema in XML. ADO.Net involves disconnected datasets because it is geared towards a distributed architecture. All tables and relations in a DataSet are exposed through the DataSet tables and Relations properties.  E.g. Using System; Using System.Data;  DataSet ds = new DataSet("MyDS"); Ds.Tables.Add ("Order"); Ds.Tables["Order"].Columns.Add("OrderNo" Type.GetType("System.Int32"));  The DataSet tightly integrates with XML using the methods WriteXml, ReadXml, WriteXmlSchema and ReadXmlSchema

Error handling that evolve around the various On Error.. statements are referred to as unstructured error handling. The build in object Err is used in this type of error handling. This object has several properties and methods as listed below: Properties:  Description: a short description of the error HelpContext: context ID for the help topic associated with the error HelpFile: fully qualified file name if any Number: Number associated with the error Source: a string that specifies the object that generated the error. Method: Clear: Clears the set values of all properties of the error object. Raise: Generates a runtime error and sets the properties of the Err object to the values supplied in the method call

Assemblies are used to specify a logical unit or building block for .net applications. A .net application contains one or more assemblies. Every assembly has version properties that include a major and a minor version, revision as well as a build number. Thus all elements of an assembly are versioned as a unit. The specifications in an assembly are referred as the assembly's manifest. To use an assembly in VB.Net project one has to follow two steps: - Add a reference of the assembly to the project. A default assembly containing the System namespace is by default added to the project. Access the members or members of the namespace in the assembly using the fully qualified class name.

The concept of namespaces plays a very crucial role in .net framework. It is a concept parallel to the concept of packages in java. In general, a namespace is a logical grouping of types for the purpose of identification. e.g. let's say in an organization there are three people with name Paul Smith each individual in a different role and responsibilities. To resolve this ambiguity we can define three namespaces based on their roles as Secretary, Manager and Operator and then reference each Paul as Secretary.Paul and Manager.Paul and Operator.Paul. This is the concept of namespace.

In order to understand the "finalize" method one needs to understand the concept of garbage collection.  The job of freeing up the memory allocated to objects is that of a garbage collector. When the garbage collector determines that an object is no longer referenced it automatically runs a special destructor function called "Finalize". However we have no way to determine when the garbage collector will call the Finalize method. We can only be sure that it will be called at some time after the last reference to the object is released. Finalize is a protected method i.e. it can be called from the class or derived classes however it cannot be called from outside of the class. If a class has a Finalize method it should explicitly call the Finalize of its base class as well.  Overrides Protected Sub Finalize ()             'Cleanup code goes here             BaseClass.Finalize End Sub

VB.Net implements a special object called Collection object that acts as a container for objects of all types. Collection can hold other objects as well as non object data. A Collection has four methods: -         Add: This method adds a member to collection. Along with data one can also specify a key value by which the data can be referenced. -         Count: This returns the total number of items in the collection object. -         Item: Retrieves an item from the collection. An item can be retrieved either using the index or a key if specified. -         Remove: Removes an item from the collection.  e.g. Dim students As New Collection students.Add ("john", "1"); //The second argument is a key to object students.Add ("paul", "2");