328 Object-Based (Web hosting account) Programming Chapter 8 The FCL allows
328 Object-Based Programming Chapter 8 The FCL allows C# programmers to achieve software reusability across platforms that support .NET and rapid applications development. C# programmers focus on the high-level programming issues and leave the low-level implementation details to classes in the FCL. For example, a C# programmer who writes a graphics program does not need to know the details of every .NET-platform graphics capability. Instead, C# programmers concentrate on learning and using the FCL s graphics classes. The FCL enables C# developers to build applications faster by reusing preexisting, extensively tested classes. In addition to reducing development time, FCL classes also improve programmers abilities to debug and maintain applications, because proven software compenents are being used. For programmers to take advantage of the FCL s classes, they must familiarize themselves with the FCL s rich set of capabilities. Software reuse is not limited to Windows-application development. The FCL also includes classes for creating Web services, which are applications packaged as services that clients can access via the Internet. Any C# application is a potential Web service, so C# programmers can reuse existing applications as building blocks to form larger more sophisticated Web-enabled applications. Many people believe that Web services represent the next phase in the evolution of software development, in which the Web provides a library of functionality from which developers can build applications in a platform-independent manner. As Microsoft s premier .NET language, C# provides all the features necessary for creating scalable, robust Web services. We formally introduce Web Services in Chapter 21, ASP .NET and Web Services. 8.16 Namespaces and Assemblies As we have seen in almost every example in the text, classes from preexisting libraries, such as the .NET Framework, must be imported into a C# program by adding a reference to the appropriate libraries (a process we demonstrated in Section 3.2). Remember that each class in the Framework Class Library belongs to a specific namespace. The preexisting code in the FCL facilitates software reuse. Programmers should concentrate on making the software components they create reusable. However, doing so often results in naming collisions. For example, two classes defined by different programmers can have the same name. If a program needs both of those classes, the program must have a way to distinguish between the two classes in the code. Common Programming Error 8.12 Attempting to compile code that contains naming collisions will generate compilation errors. Namespaces help minimize this problem by providing a convention for unique class names. No two classes in a given namespace can have the same name, but different namespaces can contain classes of the same name. With hundreds of thousands of people writing C# programs, there is a good chance the names that one programmer chooses to describe classes will conflict with the names that other programmers choose for their classes. We begin our discussion of reusing existing class definitions in Fig. 8.17, which provides the code for class Time3 (originally defined in Fig. 8.6). When reusing class definitions between programs, programmers create class libraries that can be imported for use in a program via a using statement. Only publicclasses can be reused from class libraries. Non-public classes can be used only by other classes in the same assembly.
If you are looking for cheap and quality webhost to host and run your website check Jboss Web Hosting services.