Dot Net Application Development

Visual Studio.NET is a smart tool of development that allows developing applications that target the framework of .NET. From the vista of developer, .NET consists mainly of three things that is the development environment, .NET Framework, and the .NET Framework SDK. The tool is also helpful in creating customized components and controls that can be used as a part of the application. Components are the features or objects that are used to organize, construct, and test programs of Visual Studio. The Visual Studio Toolbox window that is .NET IDE consists of all the components. These components are known as controls that are obtained from the control class and have a user interface. Some of the controls are a combination of other controls and are obtained from the User Control. The User Control objects and Form objects are developed with the VS.NET IDE designer. The easy and simple user interface is designed by dragging and dropping controls from the Toolbox window and setting the events and property values in the windows of Properties. All the set properties are stored in a .resx file for the locale. The IDE then develops the assemblies of the satellite for each locale's .resx file in the given project. The VS.NET IDE designers do not allow developing the user interface of a Control class; it allows only developing controls and components.

From the viewpoint of an expert .NET developer, the skills mentioned below are necessary for application development of .NET.

Developing Components of .NET:

Developing Controls: The important fact about a control is that it consists of a visual element, but the visual representation of a class derived from Control is not allowed by the designer of Windows Forms. Instead it shows representation of the components in the schematic manner that is used by the control while dragging from Toolbox window or the Server Explorer.

Resources and Globalization: Win32 and .NET support a different resource model. In Win32, resources are held in a section that is part of the portable executable (PE) file format and within this segment the resources are inlaid. But in.NET case, the resources are part of an assembly, but they can be inlaid within the assembly or supplied as separate files.

Resources and .NET .NET has been designed with globalization in mind. For instance, let us take an application that has been downloaded from a reliable Web site and the site is in a locale different from yours. There are different applications that are created in their own locale. If the language is different from yours, it is clear that the application has been localized to your locale and that the site gives you the downloading option of different versions that are localized. Typically this scheme is used by Win32 applications.

Civilization, Locales and Languages RFC 1766 defines the naming conventions in .NET . Civilizations are usually named with the xx-yy pattern, where xx represents the language (en for English, fr for French) while yy stands for the area where the language is used (US for United States, AU for Australia). The pattern en-US represents that English is mainly spoken in the US.