470,822 Members | 1,228 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,822 developers. It's quick & easy.

Assembly for HttpModules and HttpHandlers

Nearly all examples of writing HttpModules and HttpHandlers create them in
new assemblies. We have a lot of our common code in our "Web.Framework"
assembly - if we wrote all our modules and handlers in that framework
project, it would eliminate lots of small assemblies and Visual Studio
projects, and these classes would be available to all our apps with a simple
change of the web.config.

Are there any disadvantages in grouping all the modules and handlers with
other framework code into a single assemby - I'm thinking of maybe memory or
performance issues if a single large assembly has to be loaded several times.
Or is it smarter than this?

Many thanks

Nov 4 '08 #1
0 1011

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Aurel | last post: by
1 post views Thread by Steen Tøttrup | last post: by
6 posts views Thread by Philipp Schmid [MSFT] | last post: by
reply views Thread by tshad | last post: by
8 posts views Thread by Dale | last post: by
1 post views Thread by Anonieko | last post: by
4 posts views Thread by Jon Paal | last post: by
2 posts views Thread by kashif456 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.