In the previous articles, we saw Single-Call Remote Object and Singleton Remote Object. In this article, we will explore the usage of Generic Interface in the Remote Objects. First, we will explore how the server will register it and then move on to the client which consumes it. Generic Interface is a C# concept. But here we will explore that in Dotnet remoting context.
In this example, we will create a MFC dialog with two text boxes & a button. Then using CToolTipCtrl we will display the Tool-Tips for all three controls. To achieve this here, we derive our own class from the MFC Framework’s CToolTipCtrl.
In the previous article, we saw about the server activated Single Call remote object. Also remember, each call to the server will create a new remote object in the ‘Single Call’ technique. In this article, we will see how the Singleton Remote Objects work.
In C#, Windows Form is a User Interface (UI) that picks up input from the application users. An application can show these forms as either Modal Dialog or Modeless Dialog. Note, a Form can call some other Form and it can go deep nesting. In case of a Modal C# Dialog, the caller gets blocked till the user closes the Modal Dialog. Conversely, the Modeless C# Dialog does not block the caller. We explore these with an example.
An interface is a contract, and it is set by declaring a set of functions in it. A class can implement these interfaces. This means, we assure that a class signing the interface give an implementation for the contract functions. In this example, we will study about C# Interfaces with Examples. It covers defining & implementing, extending, implement more than one & casting between them.
The Panel Container Control is all about this article. We will see how to use the panel control for grouping the controls. Then we will explore the important properties of this container along with an example.
Panel Container is almost like a group box. Unlike the group box, the panel does not have a title on the top. But it has the support to provide the scroll bars. These scroll bars allow us to place plenty of controls in it and make us to scroll when the form is not enough to fit all the controls.
When an owner window of the menu item decides how the menu item should look, then the menu item is known as Owner Drawn Menu. The default windows provided menu has a standard look and feel. We cannot add Red and blue-colored boxes as a menu item through the resource editor. In this Example, we will see how can we display only color boxes as a menu item under the color menu. Here, we will learn the need for the WM_DRAWITEM and WM_MEASUREITEM windows messages.
1. Introduction to GroupBox Control In this article, we will explore how to use the C# ‘GroupBox Control’ in C# windows forms-based applications. Before we start, we will learn about Topmost Container, Normal Container and Controls. The first fact one should know is that a Container holds Controls in it. […]
In this article, we will learn how to push C# debugging information into the Trace File and Windows Event Logger. This is useful when the application is deployed in the customer place. Debugging an application in customer place is almost not possible as we do not keep the source code in the deployed environment.
The screen-shot below shows our Example and you can download it from the link at the bottom of this article. Here, we will not explore how the application performs prime number summation. But, will learn how to perform tracing using the C# Application Programming Interface.
We know that keyboard and mouse are basic hardware interface supported by almost all the Computer Operating System. When the user hits the keyboard key, the device driver for the keyboard deals with it by making use of the interrupts. In this example we will learn how to handle Keyboard Messages using MFC SDI Application. First, We will provide a handler function for the Keyboard. Then, inside the handler, we will check for Shift Key State and Toggle Key State.