Hi guys,

I've done many deployments of DNN over the years in all sorts of strange configurations - but this one has me stumped at the moment.

My web server runs a MS Commerce server site on the 'default' web.  Due to the nature of this deployment, I have no ability to play around with either the machine.config or the root web.config (I do however have copies of both at my disposal)

I have deployed my DNN site in a virtual directory (in a separate app pool) which works fine if i reference it by an IP address assigned to the virtual directory (which has been fine for testing) but in the real world I must deploy the DNN site to www.domain.com/blah/dnn  (for example)

Now - if I just deploy the standards web.config in the dnn directory - it of course complains about the many missing modules etc. 

I've tried copying the modules in question to the 'bin' directory - and 'removing' them from web.config in my dnn domain this throws up further error after error...

I tried 'clearing' the modules from the web.config - which results in the DNN site being browsable, but then it is not possible to 'login' - it does however allow a user to register - and it actually 'works' in that it sends the confirmation email etc.

So - close but no cigar.

anyone got any suggestions as to any module that i specifically need to 're-include' (beyond the standard dnn ones in web.config) after using the clear function to get authentication to work?

Many thanks!

Ben

Thanks for taking the time to reply Julian, but you've totally missed the nature of the problem...

I have no issue 'moving' a DNN site / database etc.

The problem is to do with inheritance (standard IIS behavior) of modules and configuration within the web.config

I've got COMMERCE SERVER installed on the 'default' web - which is essential to the running of my company primary website.

I'm setting up a DNN portal, to serve a specific purpose for a 'community' aspect of our business

www.company.com/community

where community is my DNN portal

the problem is that settings in the default web.config (and machine.config for that matter) are inherited by my 'sub-web'  because of the many assemblies as a part of the commerce server site - first - dnn would not run at all.

I spent many hours 'trying' to explicitly 'remove' all assemblies/modules/handlers from the web.config for the DNN application - but with no success.

eventually - taking the sledgehammer approach - I have used the tag - < clear /> within the httpModules section which has NEARLY got the site working.

Ie - the site is browsable however a couple of significant issues remain.

1.  Images are not rendered

2. (and more significantly) Sign in is not possible.  I can see from my SQL logs, that it performs the validation of the user account - however it seems that IIS is not effectively creating a session for the validated user.

I'm really starting to tear my hair out over this - and cant believe that ultimately i dont just have to 'add' a couple of httpModules or something to resolve it in web.config.

ANYONE?  (ps - this is not a question for people who don't really understand the workings of assemblies/web.config/IIS etc)

thanks! - free beer for whoever solves this one...

I'm not very familiar with commerce sever... but if you can create a new website instead of a virtual directory then you will not have any problems with web.config clashes.

JK.