Hi,

Not really a module-specific question - I'm trying to avoid having to write one if anything!

I've got a an ASP.NET web site which I've ported to DotNetNuke. Everything's fine apart from a Contact web form which sits as an IIS application under the ASP.NET web site's folder structure. It has some compiled code which forwards a user's details to a web service.

Ideally, I wanted to simply copy the application folder to the DotNetNuke folder structure and write my own form which would submit data to the Contact application (an .aspx page with some pre-compiled code-behind). Unfortunately, it doesn't seem to work and fails with an error as follows:

Could not load file or assembly 'DotNetNuke.HttpModules' or one of its dependencies. The system cannot find the file specified.

The application has its own bin folder and web.config file which had authentication set to "Windows" - I duly changed this of course but it made no difference. I converted the folder to an application under IIS as well, but still no luck.

Any ideas?

Hi Sebastian,

Thanks for your reply.

The web application is now in a file structure outside the DNN folder structure. I added a Virtual Directory under the DNN folder and pointed it at the web application but I still get the same issue. I presume the child application's web config would need to be changed in some arcane manner to work around the issue?

I added a basic HTML file as a quick test - I could access this but as soon as I converted the virtual folder to an application under IIS, even that HTML file was no longer available. I think it's because the child application (and it still is even though it's a virtual folder or sat within the DNN folder as you'll know) is inheriting the DNN web.config. I beieve I can configure the web.config file not to be inherited by the virtual directory by wrapping the system tag with a location tag:

location path="." inheritInChildApplications="false"

...but this is a change to the DNN web config which isn't exactly ideal is it? If I could change the child application's web.config to force it to ignore the containing application's (DNN) web.config, that wouldn't be so bad.

Regards,

Darrin