Dot net Application Development
Visual Studio .NET is an intelligent development tool that allows developing applications that target the .NET Framework. From a developer’s vista, .NET enterprises of three things viz., The .NET Framework, the .NET Framework SDK, and the development environment. The tool is also used to create customized controls and components that can be used as a part of the application. Components are objects or the features that are used to construct, organize and test Visual Studio programs. The Toolbox window of the Visual Studio .NET IDE contains all the components. Components are considered as controls that are derived from the Control class and have a user interface. Some controls are a combination of other controls and are derived from the User Control. The User Control objects and Form objects can be developed with the designer of the VS.NET IDE. A simple user interface can be designed by dragging and dropping controls from the Toolbox window and setting the property values and events in the Properties window. All the properties that are set are stored in a .resx file for the locale. The IDE then builds the satellite assemblies for each locale’s .resx file in your project. The VS.NET IDE designer does not allow developing the user interface of a Control class; it only allows developing components and controls.
From the perspective of a good .NET developer, the below mentioned skills are very much essential for developing .NET applications.
.NET Developing Components:
Developing Controls: The vital fact about a control is that it has a visual element, but the visual representation of a class derived from Control is not allowed by the Windows Forms designer. Instead it shows the schematic representation of the components that the control uses while dragging from the Server Explorer or Toolbox window.
Resources and Internationalization: .NET and Win32 support a different model of resources. In Win32, resources are held in a section that is part of the portable executable (PE) file format and the resources are inlaid within this segment. But in the case of.NET, 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 internationalization in mind. For example, let us consider an application that has been downloaded from a trusted Web site and the Web site is in a locale different from yours. There are various applications that are created in their own locale. If the language is different from yours, it is obvious that the application has been localized to your locale and that the web site gives you the option of downloading different localized versions. This scheme is typically used by Win32 applications.
Locales, Civilization, and Languages Naming conventions in .NET are defined in RFC 1766. Civilizations are generally named with the pattern xx-yy, where xx represents the language (en for English, fr for French) while yy represents the area where the language is used (AU for Australia, US for United States). The pattern en-US represents that English is spoken in the US.