Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jun 06, 2011 03:54 PM by robinwhitehead2
Jun 06, 2011 03:54 PM|LINK
We recently upgraded to VS2010 and .NET 4.0 (we were previously on VS2005 and .NET 2.0). We're still using Windows Server 2003, so are forced to still use IIS 6.
One of our websites uses a custom HttpModule that sets a custom Response.Filter. This causes a 404 error when navigating (or posting) to the site's default document (as specified in the IIS control panel). This was previously working fine under .NET 2.0, and
its only when moving up to .NEt 4.0 that we started seeing this. I know everything else on the web server is setup OK, since our other websites (that don't do this) are working fine, and when I remove the declaration reference to the custom HttpModule from
the broken site's web.config, it starts working again (albeit without the additional functionality that the HttpModule was providing - which is crucial functionality)
Does anyone know how to get around this?