Do you know how the Table works in html? The “TableLayoutPanel” works almost the same way how the table works in html. In this example, we will see how the C# TableLayoutPanel can be used & how each cell of this panel behaves. Also, we will nest some other layout panel with this one. At the end we will see a small professional looking form that can be used by any hospital management application.
OK. The C# TableLayoutPanel is collection cells and these cells can be arranged in rows and columns. We can imagine each cell as a special container. Why we say that it is a special container? Because each cell can hold only one control in it. What if we need to have multiple controls in one cell? Actually, that is not required most of the time for this container. But if we still need an answer, place a container you like in that cell and start placing the controls inside the container which occupying the cell. Say, for example, we can place a Panel in a cell and add multiple controls to that Panel.
A Strip is a nearly thin slice of an object. Dot net has three great strip controls, namely MenuStrip, StatusStrip and ToolStrip. In this Example, we will explore the C# MenuStrip and ContextMenuStrip Controls.
All the strip controls accommodate some other UI elements in it. A menu strip allows us to add Menu and Menu allows us to add Menu Items. Similarly, the ToolStrip control allows us to add one or more Tool Bar buttons in it. OK, let us go to the MenuStrip. The below screenshot shows our example:
The C# FlowLayoutPanel Container keeps the controls in a specific flow. When user resizes the container, it works out the controls so that the flow is kept intact. In this example, we will place some controls inside the FlowLayoutPanel Container and learn some vital properties and methods that control the container’s content.
ASP’s AdRotator Control is useful for showing the Ads. This control acts as a placeholder for the image and the image is actually a link to the advertised website. AdRotator control regularly changes the image display and when the user clicks the image, they navigate to the target website. To use AdRotator, we must first create the images to the external websites. Then an XML file tells the AdRotator Control which site to navigate when a user clicks the image.
Tab Controls arranges related controls in a group and shows that as a Tab Page. This C# example shows how to create Tab Pages dynamically and add it to the tab control. Then the example shows displaying the Tabs in multiple lines, changing its alignment and Tab button styles.
In the past articles, we read about “Server Activated” remote objects. We also ran through separate article for Single Call and Singleton on the Server activated remote objects. In this post, we will try how to use the “Client activated” remote objects.
Before we go on Client Activated remote objects, we have to know what is activation and where the object lives. The clear fact whether it is server activated or client activated is that the remote object lives in the “Remote Pool” of the server. Client activation means, the client sets up the object on the server’s remote pool using the operator new in the client. So, if you are building up a class for the Client Activated Remote object, you have the power of using the overloaded constructors.
In this article, we will explore how one can use a delegate on the functions exposed by the remote objects. Also, we will see how do we call those remote object functions as synchronous and asynchronous. Basic knowledge on threading will help you catch this article in a better way but not a mandate.
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 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.