http://blogs.iis.net/ksingla/archive/tags/httpserv.h/default.aspxTags: httpserv.henCommunityServer 2007 SP1 (Build: 20510.895)http://blogs.iis.net/ksingla/archive/2009/01/01/generating-trace-information-in-native-modules.aspxThu, 01 Jan 2009 19:36:00 GMT50bcf3b4-f6fe-4638-adff-0c150e922e99:2841538ksingla4http://blogs.iis.net/ksingla/rsscomments.aspx?PostID=2841538http://blogs.iis.net/ksingla/archive/2009/01/01/generating-trace-information-in-native-modules.aspx#commentsIIS7 has really nice tracing capabilities which are available to all module developers. If you want to make it easy for you and your customers to debug problems in your modules, you should definitely be using them. You can use IHttpTraceContext::RaiseTraceEvent...(<a href="http://blogs.iis.net/ksingla/archive/2009/01/01/generating-trace-information-in-native-modules.aspx">read more</a>)<img src="http://blogs.iis.net/aggbug.aspx?PostID=2841538" width="1" height="1">httpserv.hhttp://blogs.iis.net/ksingla/archive/2008/12/21/using-imetadatainfo-getmodulecontextcontainer-to-store-configuration-data.aspxMon, 22 Dec 2008 04:05:00 GMT50bcf3b4-f6fe-4638-adff-0c150e922e99:2823377ksingla4http://blogs.iis.net/ksingla/rsscomments.aspx?PostID=2823377http://blogs.iis.net/ksingla/archive/2008/12/21/using-imetadatainfo-getmodulecontextcontainer-to-store-configuration-data.aspx#commentsIf you write an IIS7 module, you would typically want to control its behavior based on some configuration data. IIS7 makes it really easy for developers to extend configuration schema so that their customers can put configuration data for their modules...(<a href="http://blogs.iis.net/ksingla/archive/2008/12/21/using-imetadatainfo-getmodulecontextcontainer-to-store-configuration-data.aspx">read more</a>)<img src="http://blogs.iis.net/aggbug.aspx?PostID=2823377" width="1" height="1">httpserv.h