Hi Jo & Co,

Sorry if I'm missing the blindingly obvious here but this has had me stumped since yesterday, when my client was expecting to go live and is now getting rather cross!

We have a client with a PHP based CMS and an ASP.NET based (ASPDOTNETSTOREFRONT) online store.

The client site is at www.cwr.org.uk and the store sits "under" this as a separate IIS application so it's accessible at www.cwr.org.uk/store.  All this has been working happily for the last couple of years.

We recently persuaded the client to upgrade their CMS to Mojo, with the idea being that www.cwr.org.uk would now be Mojo with www.cwr.org.uk/store continuing as an AspDotNetStoreFront application.

But having tried it on the development server I've discovered that it doesn't work.  It looks like Mojo's URL re-writer (understandably) catches any reference to /store as being part of the mojo site and a range of errors results.

Is there any way to to tell Mojo to not look at anything under the /store node so that it can leave the underlying application to get on with doing it's own thing independantly?

All thoughts welcome!

Thanks

Ian

Hi Jo,  thanks for the reply. 

I've modified my web.config to wrap <location...> around <system.web> as per your link but I'm still getting problems.  If I try and run the web store as-is (but with the above change) I get

"Could not load file or assembly 'mojoPortal.Web' or one of its dependencies. The system cannot find the file specified. "

If I copy the various mojo dlls into the bin dir on my child site I then get the error

"Could not find a part of the path 'D:\Websites\StoreFront\CWR\CwrStore_Live_8_1_2\Web\Data\Sites\1\systemfiles\sitesettingscachedependecy.config'. "

It was that that made me think that the URL rewriter was trying to do something weird with the sub-site, but do you think the fault may lie elsewhere?

Thanks again,

Ian

Jo you're a genius!

I'd wrapped system.web but not the system.webserver section!

All now looking much more hopeful.

Thanks again - beer on the way!

Ian