|
|
You'll have to adjust quite a lot of things with ASP.NET version 2.0. You've heard about new options and features in the various chapters of this book, all of which are waiting for you to configure them to your liking. Due to space restrictions, however, this book can't completely cover this topic. Therefore, I'd like to recommend taking a look at the machine.config configuration file. There really is a lot to discover in this file.
This chapter isn't dedicated to configuration settings, but demonstrates the various new possibilities they provide and how to edit them. Naturally, you can still edit the web.config configuration file directly within the development environment or even by means of a simple text editor. But maybe there is a little more convenience ahead for you?
You've already heard about the new Web Site Administration tool in Chapter 6. As I also discussed in that chapter, the Security Setup Wizard can be used to configure the security settings of a web site. Actually, the possibilities of the tools are limited to these settings. Some further developments are being planned for the Beta version.
You can reach the tool, shown in Figure 13-1, through the following URL:
http://localhost/<application>/webadmin.axd
Of course, this tool has been created completely in ASP.NET and is available in the following directory in the source code:
<windir>\Microsoft.NET\Framework\<version>\ASP.NETWebAdminFiles
The source code will help you to get a better understanding of ASP.NET with regard to configuration on the one hand. On the other hand, it forms the basis for individual changes and above all for enhancements. Instead of developing your own admin tool for your web site, you can expand the existing tool with the required functions from now on. ISPs as well can offer an enhanced tool to their customers this way.
Actually, you can only set up and enhance the tool globally with the machine.config configuration file. Within the <webSiteAdministrationTool> section, you can not only define whether the tool is active, but also who will get the right to access it. According to the default setting, all users have the right to access the tool from the local machine. Any access from outside the machine will be declined. Integration with the user management system makes particularly sense for productive systems.
|
|
