Hi,

On deploying a site with Site Manager Export, I have come across an issue
with my current site structure.  Namely that my main ASP.Net application is
in the root site directory (including web.config and global.asax), which
causes a conflict with the web application MCMS nested under the root dir.

I have seen the posting of identical name to this thread and quote:
"
Hi Chandy,


the web.config needs to be at the root of your template project.
And the template project should not be in the root of your web site.
Actually it seems in your situation you have placed the template project in
the root.


There are two way to correct this:


1) move your template project to a sub folder (don't forget to also move the
CMS virtual directory) and correct the template file binding in your
template gallery items
2) create a second web site pointing to an empty folder and enable this as
an MCMS entry point using the SCA. Then point SiteManager to this new web
site which then does not have a web.config in the root.


Cheers,
Stefan.


"

I have couple of questions and a point to make:

In the section "MCMS Projects in Visual Studio .Net" Oct 2003 edition it,
after "To create a new MCMS project" it talks about the differences between
MCMS projects and normal ASP.Net projects.
It says "
a.. Creating an MCMS virtual directory under the application directory for
the project, allowing more convenient referencing of MCMS components. "

I guess this is wrong. I tried getting the updated chm file, but I can't
read it.  I get an unknown publisher message, and then none of the content
pages show.

I want to have forms based login for any of the pages on the CMS site. So
far I achieved this by modifying the web.config in the root directory, but
this is no longer okay.  I am guessing I need to have the forms
authentication configuration set up in the web.config in my "template
project".  Is this correct?

It feels like this directory structure requirement is quite subtle and not
spelt out anywhere(?)

Thanks
Martin

[ Post a follow-up to this message ]

Quick update.

I've realised how show the chm properly, however it doesn't seem to have
anything/much about developing MCMS sites.  Can't see anything about the
directory structure requirements.  Am I wrong?

Thanks again
Martin

"Martin" <x@y.z> wrote in message
news:%23ixftkbHGHA.3144@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> On deploying a site with Site Manager Export, I have come across an issue
> with my current site structure.  Namely that my main ASP.Net application
> is in the root site directory (including web.config and global.asax),
> which causes a conflict with the web application MCMS nested under the
> root dir.
>
> I have seen the posting of identical name to this thread and quote:
> "
> Hi Chandy,
>
>
> the web.config needs to be at the root of your template project.
> And the template project should not be in the root of your web site.
> Actually it seems in your situation you have placed the template project
> in
> the root.
>
>
> There are two way to correct this:
>
>
> 1) move your template project to a sub folder (don't forget to also move
> the
> CMS virtual directory) and correct the template file binding in your
> template gallery items
> 2) create a second web site pointing to an empty folder and enable this as
> an MCMS entry point using the SCA. Then point SiteManager to this new web
> site which then does not have a web.config in the root.
>
>
> Cheers,
> Stefan.
>
>
> "
>
> I have couple of questions and a point to make:
>
> In the section "MCMS Projects in Visual Studio .Net" Oct 2003 edition it,
> after "To create a new MCMS project" it talks about the differences
> between MCMS projects and normal ASP.Net projects.
> It says "
> a.. Creating an MCMS virtual directory under the application directory for
> the project, allowing more convenient referencing of MCMS components. "
>
> I guess this is wrong. I tried getting the updated chm file, but I can't
> read it.  I get an unknown publisher message, and then none of the content
> pages show.
>
> I want to have forms based login for any of the pages on the CMS site. So
> far I achieved this by modifying the web.config in the root directory, but
> this is no longer okay.  I am guessing I need to have the forms
> authentication configuration set up in the web.config in my "template
> project".  Is this correct?
>
> It feels like this directory structure requirement is quite subtle and not
> spelt out anywhere(?)
>
> Thanks
> Martin
>

[ Post a follow-up to this message ]

Hi Martin,

if a web.config is located in the root of the site it will interact with the
web.config inside the /MCMS web application.
And this causes Site Deployment to fail.

Either create a second website configured as read-write entry point with
empty root or move your web application away from the root.

Cheers,
Stefan

--
This posting is provided "AS IS" with no warranties, and confers no rights

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------


"Martin" <x@y.z> wrote in message
news:e0FdirbHGHA.1032@TK2MSFTNGP12.phx.gbl...
> Quick update.
>
> I've realised how show the chm properly, however it doesn't seem to have
> anything/much about developing MCMS sites.  Can't see anything about the
> directory structure requirements.  Am I wrong?
>
> Thanks again
> Martin
>
> "Martin" <x@y.z> wrote in message
> news:%23ixftkbHGHA.3144@TK2MSFTNGP10.phx.gbl... 
>
>

[ Post a follow-up to this message ]