Here I am again, the rookie from hell.

In the applicationHost.config file, we have section groups and sections. I
understand those. I'm kind of lost on what one element is referred to in
applicationHost.config. Here is a small example:

<system.webServer>
<modules>
<add name="HttpCacheModule"/>
<add name="Profile" type="System.Web.Profile.ProfileModule">
</modules>
</system.webServer>

Are the elements or lines with the "add name" in them referred to as
features in the hierarchy?

TIA

Re: applicationHost.config and features by David

David
Fri Mar 30 07:07:01 CDT 2007

<add> are elements of a collection. In this case, you are refering to
the <modules> collection.

It happens that when you install "Components" within Vista that some
translate into adding modules and globalModules, but there is no
direct connection between "features" and "add" elements.

For example, adding ISAPI component leads to "isapi" module being
added, but adding the ASP component does not add any more modules. It
adds handlers instead.

Depending on the configuration properties, you are really asking about
different parts of IIS7 architecture. When you ask about
<globalModules>, <modules>, <handlers>, you are really asking about
the core Integrated Pipeline that we designed in IIS7, and without
understanding that design, the configuration is not going to make
sense.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Mar 29, 8:30 pm, "dogface" <pwhitl...@carolina.rr.com> wrote:
> Here I am again, the rookie from hell.
>
> In the applicationHost.config file, we have section groups and sections. I
> understand those. I'm kind of lost on what one element is referred to in
> applicationHost.config. Here is a small example:
>
> <system.webServer>
> <modules>
> <add name="HttpCacheModule"/>
> <add name="Profile" type="System.Web.Profile.ProfileModule">
> </modules>
> </system.webServer>
>
> Are the elements or lines with the "add name" in them referred to as
> features in the hierarchy?
>
> TIA



Re: applicationHost.config and features by dogface

dogface
Fri Mar 30 12:40:10 CDT 2007

Let me ask it this way.

I understand that the old metabase has been replaced primarily by
applicationHost.config and I understand the hierarch to a degree.
For instance I understand what a location tag is and you use it to unlock
sections. I know that <system.webServer> is a section group. My feeling is
that in the example below <handlers accessPolicy="Read, Script"> is a
section though I don't understand the accessPolicy piece. The add name sort
of confuses me in that is this a setting? Does "add name" create a setting?
Below is an example from the applicationHost.config (the add name is quite
long so I cut out most of it) though shortened to try to get each part in.
I've put in brackets what I think each part is.

<location path="" overrideMode="Allow"> (location tag)
<system.webServer> (section group)
<handlers accessPolicy="Read, Script"> (section ?)
<add name="TraceHandler-Integrated" path=.....>
(setting ?)
</handlers>
<system.webServer>
</location>

I've been given the task of understanding IIS 7.0. I'm a networking guy
(IGRP, OSPF, DNS, NAT, PAT, etc.) those are things I'm comfortable with but
I've been tasked to learn this by my company.

All help is appreciated and I apologize for my ignorance on this subject. I
know what it's like to deal with a newbie and now I'm one again. Humbling
to say the least.

"David Wang" <w3.4you@gmail.com> wrote in message
news:1175256421.868338.257280@o5g2000hsb.googlegroups.com...
> <add> are elements of a collection. In this case, you are refering to
> the <modules> collection.
>
> It happens that when you install "Components" within Vista that some
> translate into adding modules and globalModules, but there is no
> direct connection between "features" and "add" elements.
>
> For example, adding ISAPI component leads to "isapi" module being
> added, but adding the ASP component does not add any more modules. It
> adds handlers instead.
>
> Depending on the configuration properties, you are really asking about
> different parts of IIS7 architecture. When you ask about
> <globalModules>, <modules>, <handlers>, you are really asking about
> the core Integrated Pipeline that we designed in IIS7, and without
> understanding that design, the configuration is not going to make
> sense.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>
>
>
> On Mar 29, 8:30 pm, "dogface" <pwhitl...@carolina.rr.com> wrote:
>> Here I am again, the rookie from hell.
>>
>> In the applicationHost.config file, we have section groups and sections.
>> I
>> understand those. I'm kind of lost on what one element is referred to in
>> applicationHost.config. Here is a small example:
>>
>> <system.webServer>
>> <modules>
>> <add name="HttpCacheModule"/>
>> <add name="Profile"
>> type="System.Web.Profile.ProfileModule">
>> </modules>
>> </system.webServer>
>>
>> Are the elements or lines with the "add name" in them referred to as
>> features in the hierarchy?
>>
>> TIA
>
>


Re: applicationHost.config and features by David

David
Fri Mar 30 16:19:51 CDT 2007

Thanks for the clarification.

This is interesting info for me to compose a blog entry on, so that is
what I will reply with.

It is at least doubly hard for you because you are learning both a new
configuration system as well as new server core.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Mar 30, 10:40 am, "dogface" <pwhitl...@carolina.rr.com> wrote:
> Let me ask it this way.
>
> I understand that the old metabase has been replaced primarily by
> applicationHost.config and I understand the hierarch to a degree.
> For instance I understand what a location tag is and you use it to unlock
> sections. I know that <system.webServer> is a section group. My feeling is
> that in the example below <handlers accessPolicy="Read, Script"> is a
> section though I don't understand the accessPolicy piece. The add name sort
> of confuses me in that is this a setting? Does "add name" create a setting?
> Below is an example from the applicationHost.config (the add name is quite
> long so I cut out most of it) though shortened to try to get each part in.
> I've put in brackets what I think each part is.
>
> <location path="" overrideMode="Allow"> (location tag)
> <system.webServer> (section group)
> <handlers accessPolicy="Read, Script"> (section ?)
> <add name="TraceHandler-Integrated" path=.....>
> (setting ?)
> </handlers>
> <system.webServer>
> </location>
>
> I've been given the task of understanding IIS 7.0. I'm a networking guy
> (IGRP, OSPF, DNS, NAT, PAT, etc.) those are things I'm comfortable with but
> I've been tasked to learn this by my company.
>
> All help is appreciated and I apologize for my ignorance on this subject. I
> know what it's like to deal with a newbie and now I'm one again. Humbling
> to say the least.
>
> "David Wang" <w3.4...@gmail.com> wrote in message
>
> news:1175256421.868338.257280@o5g2000hsb.googlegroups.com...
>
>
>
> > <add> are elements of a collection. In this case, you are refering to
> > the <modules> collection.
>
> > It happens that when you install "Components" within Vista that some
> > translate into adding modules and globalModules, but there is no
> > direct connection between "features" and "add" elements.
>
> > For example, adding ISAPI component leads to "isapi" module being
> > added, but adding the ASP component does not add any more modules. It
> > adds handlers instead.
>
> > Depending on the configuration properties, you are really asking about
> > different parts of IIS7 architecture. When you ask about
> > <globalModules>, <modules>, <handlers>, you are really asking about
> > the core Integrated Pipeline that we designed in IIS7, and without
> > understanding that design, the configuration is not going to make
> > sense.
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //
>
> > On Mar 29, 8:30 pm, "dogface" <pwhitl...@carolina.rr.com> wrote:
> >> Here I am again, the rookie from hell.
>
> >> In the applicationHost.config file, we have section groups and sections.
> >> I
> >> understand those. I'm kind of lost on what one element is referred to in
> >> applicationHost.config. Here is a small example:
>
> >> <system.webServer>
> >> <modules>
> >> <add name="HttpCacheModule"/>
> >> <add name="Profile"
> >> type="System.Web.Profile.ProfileModule">
> >> </modules>
> >> </system.webServer>
>
> >> Are the elements or lines with the "add name" in them referred to as
> >> features in the hierarchy?
>
> >> TIA- Hide quoted text -
>
> - Show quoted text -