Httpmodules, Sub-Applications and Clear

[Markus Kling]

Hi,

I have a web application that has two sub-applications. The root application
defines two httpModules which shall not be loaded for the subapplications. I
tried to achieve this by adding

<httpmodules>
<clear />
</httpmodules>

within the web.config file of the sub-applications.

My problem is that the compiler stil tries to load the referenced assemblies
and states them (correctly) as missing.

What did I miss?

Thanks
Markus

 

[Juan T. Llibre]

<clear /> removes HttpModule mappings from an application.

<remove name=...> removes the HttpModule class from an application.

<httpModules>
<add type="classname,assemblyname" name="modulename"/>
<remove name="modulename"/>
<clear/>
</httpModules>

 

[Markus Kling]

Hi Juan,

that's exactly what I did!!

wwwroot\web.config
....
<httpModules>
<add type="NK.Utils.LogInitializer,NK.Utils" name="LogInitializer" />
<add type="awisto.Web.UrlRewrite.HttpModule,awisto.Web.UrlRewrite"
name="UrlRewrite" />
</httpModules>
...

wwwroot\subapp\web.config
....
<httpmodules>
<clear />
</httpmodules>
....

This results in a Pre-bin failure for the NK.Utils dll within the
"wwwroot\subapp" application. That's correct since the DLL is not in the
wwwroot\subapp\bin directory.

My question was why it is not removed!!

Thanks again,
Markus

 

[Juan T. Llibre]

Doesn't, in wwwroot\subapp\web.config :

<httpModules>
<remove name="LogInitializer"/>
<remove name="UrlRewrite"/>
<clear />
</httpModules>

work ?

 

[Markus Kling]

No, that's exactly what's confuses me.

 

[Juan T. Llibre]

Hi, Mark.

OK, from your post it wasn't clear whether you were removing
the modules by using <remove name="LogInitializer"/> and
<remove name="UrlRewrite"/> since you only included <clear />
in your reply.

If that's the case, I'd bug it at the Feedback Center :

http://lab.msdn.microsoft.com/productfeedback/

You'll need a Passport account to be able to file bug reports there.

 

[Markus Kling]

Just to be clear. The issues are for .Net 1.2. Haven't crosschecked with
..Net 2.0 runtime.

Markus

 

[Juan T. Llibre]

<remove...> works the same way in 1.1.

See :
http://msdn.microsoft.com/library/d...s/cpgenref/html/gngrfremoveforhttpmodules.asp
and
http://msdn.microsoft.com/library/d...-us/cpgenref/html/gngrfhttpmodulessection.asp
for 1.1

and
http://msdn2.microsoft.com/en-us/library/81b3ekbd.aspx
for 2.0

The only caveat is that the value of <remove>
must exactly match that of a previous <add> directive.

 

[Markus Kling]

My configration is definitly correct.
Should be a bug.

Markus

 

[Markus Kling]

Someone having the same problem...
http://discuss.develop.com/archives/wa.exe?A2=ind0302d&L=dotnet-web&T=0&F=&S=&P=10801

 

[Juan T. Llibre]

Definitely, bug it.

 

[Scott Allen]

Someone having the same problem...
http://discuss.develop.com/archives/wa.exe?A2=ind0302d&L=dotnet-web&T=0&F=&S=&P=10801

Yes, that's been a 'problem' for a long time. The only workaround I've
found is to copy assemblies from the parent into the sub apps.

http://odetocode.com/Blogs/scott/archive/2004/01/07/145.aspx