26 CHAPTER 1 THE PHILOSOPHY OF .NET (Web server extensions)
26 CHAPTER 1 THE PHILOSOPHY OF .NET Depending on the development tool you are using to build your .NET applications, you will have various ways to inform the compiler which assemblies you wish to include during the compilation cycle. You ll examine how to do so in the next chapter, so I ll hold off on the details for now. Using ildasm.exe If you are beginning to feel a tad overwhelmed at the thought of gaining mastery over every namespace in the .NET platform, just remember that what makes a namespace unique is that it contains types that are somehow semantically related. Therefore, if you have no need for a user interface beyond a simple console application, you can forget all about the System.Windows.Forms and System.Web namespaces (among others). If you are building a painting application, the database namespaces are most likely of little concern. Like any new set of prefabricated code, you learn as you go. The Intermediate Language Disassembler utility (ildasm.exe) allows you to load up any .NET assembly and investigate its contents, including the associated manifest, CIL code, and type metadata. By default, ildasm.exe should be installed under C:Program FilesMicrosoft Visual Studio 8SDKv2.0Bin (if you cannot find ildasm.exe in this location, simply search your machine for a file named ildasm.exe ). Once you locate and run this tool, proceed to the File .Open menu command and navigate to an assembly you wish to explore. By way of illustration, here is the CSharpCalculator.exe assembly shown earlier in this chapter (see Figure 1-6). ildasm.exe presents the structure of an assembly using a familiar tree-view format. Figure 1-5. The base class libraries reside in the GAC.
Check Tomcat Web Hosting services for best quality webspace to host your web application.