Our site works well in development (http://[servername]/ltaonlinev2/) bu
t
when we move it to the authoring server (http://author.lta.org.uk) which map
s
channels to host headers it all breaks down.

This is because the template is looking for a template file in
/ltaonlinev2/templates which, as we are mapping channels to host headers, no
longer exists....

Please help.

thanks

John

[ Post a follow-up to this message ]

Hi Lta,

you need to ensure that the same directory structure exists on both servers.
This is independend from the map channel name to host header name feature as
the files in this directory are never directly called -  only indirectly.

Only the channel path is affected by the "map channel name to host header
name" feature. Not the files and directories on the file system.

Cheers,
Stefan


"Lta" <Lta@discussions.microsoft.com> schrieb im Newsbeitrag
news:84D30F44-5DCA-4D33-BE6E-24014FB584E5@microsoft.com...
> Our site works well in development (http://[servername]/ltaonlinev2/) 
but
> when we move it to the authoring server (http://author.lta.org.uk) which
> maps
> channels to host headers it all breaks down.
>
> This is because the template is looking for a template file in
> /ltaonlinev2/templates which, as we are mapping channels to host headers,
> no
> longer exists....
>
> Please help.
>
> thanks
>
> John

[ Post a follow-up to this message ]

Hi Stefan,

The directory structure is exactly the same between servers. This has been
verified using Beyond Compare. The entry points also point to exactly the
same directory, this is the problem I think....

In Dev, the 'virtual directory' entrypoint http://localhost/ltaonlinev2/
points to the same directory as the 'website' authoring entrypoint
http://author.lta.org.uk/. This is the point, the virtual directory
'/LtaonlineV2/' does not exits on the authoring or live servers.

As you explained to me in a previous post, microsoft only support one
development website which, because it is being developed using Visual Studio
,
must run through localhost and therefore in a multisite development
environment must use Virtual Directories. However on the authoing and live
servers, the archectecture changes slightly and we no longer use localhost
but map channels to host headers instead.

The 'LtaOnlineV2' virtual directory has become a website and the
'/Ltaonlinev2/' part of 'http://localhost/ltaonlinev2/' is invalid.

If I add the virtual directory /ltaonlivev2/ to the website it errors
because it points to itself. If I move the IIS directory up one level to
LtaOnlineSolutionV2 the site does not run because it cannot run the compiled
base class and the global.asax and web.config files are in the wrong
directory.

Please tell me what the recomended architecture between dev and live should
be.

Thanks, John


"Stefan [MSFT]" wrote:

> Hi Lta,
>
> you need to ensure that the same directory structure exists on both server
s.
> This is independend from the map channel name to host header name feature 
as
> the files in this directory are never directly called -  only indirectly.
>
> Only the channel path is affected by the "map channel name to host header
> name" feature. Not the files and directories on the file system.
>
> Cheers,
> Stefan
>
>
> "Lta" <Lta@discussions.microsoft.com> schrieb im Newsbeitrag
> news:84D30F44-5DCA-4D33-BE6E-24014FB584E5@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi Lta,

but it seems that the SourceFile property of the template gallery items are
pointing to the /ltaonlinev2/templates folder.
Please double check using MCMS template explorer.

Cheers,
Stefan


"Lta" <Lta@discussions.microsoft.com> schrieb im Newsbeitrag
news:DC0936AB-C801-42FD-B5D5-C91F98075E65@microsoft.com...[vbcol=seagreen]
> Hi Stefan,
>
> The directory structure is exactly the same between servers. This has been
> verified using Beyond Compare. The entry points also point to exactly the
> same directory, this is the problem I think....
>
> In Dev, the 'virtual directory' entrypoint http://localhost/ltaonlinev2/
> points to the same directory as the 'website' authoring entrypoint
> http://author.lta.org.uk/. This is the point, the virtual directory
> '/LtaonlineV2/' does not exits on the authoring or live servers.
>
> As you explained to me in a previous post, microsoft only support one
> development website which, because it is being developed using Visual
> Studio,
> must run through localhost and therefore in a multisite development
> environment must use Virtual Directories. However on the authoing and live
> servers, the archectecture changes slightly and we no longer use localhost
> but map channels to host headers instead.
>
> The 'LtaOnlineV2' virtual directory has become a website and the
> '/Ltaonlinev2/' part of 'http://localhost/ltaonlinev2/' is invalid.
>
> If I add the virtual directory /ltaonlivev2/ to the website it errors
> because it points to itself. If I move the IIS directory up one level to
> LtaOnlineSolutionV2 the site does not run because it cannot run the
> compiled
> base class and the global.asax and web.config files are in the wrong
> directory.
>
> Please tell me what the recomended architecture between dev and live
> should
> be.
>
> Thanks, John
>
>
> "Stefan [MSFT]" wrote:
> 

[ Post a follow-up to this message ]

On dev that is correct as the MCMS template explorer starts off at localhost
,
but this doesn't work on the live or authoring servers as we are not using
localhost.

I cannot check this on live or authoring as VS is not installed but it will
be wrong as there is no /LtaOnlineV2/ root directory. Surley we are not
expected to change the properties of the template once we move them to live?
??

"Stefan [MSFT]" wrote:

> Hi Lta,
>
> but it seems that the SourceFile property of the template gallery items ar
e
> pointing to the /ltaonlinev2/templates folder.
> Please double check using MCMS template explorer.
>
> Cheers,
> Stefan
>
>
> "Lta" <Lta@discussions.microsoft.com> schrieb im Newsbeitrag
> news:DC0936AB-C801-42FD-B5D5-C91F98075E65@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi Lta,

the MCMS developer tools are not supported and do not work correct if the
servername is different from "localhost".

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
----------------------


"Lta" <Lta@discussions.microsoft.com> wrote in message
news:F8473973-1A73-417D-98A6-6D09F957D57C@microsoft.com...[vbcol=seagreen]
> On dev that is correct as the MCMS template explorer starts off at
> localhost,
> but this doesn't work on the live or authoring servers as we are not using
> localhost.
>
> I cannot check this on live or authoring as VS is not installed but it
> will
> be wrong as there is no /LtaOnlineV2/ root directory. Surley we are not
> expected to change the properties of the template once we move them to
> live???
>
> "Stefan [MSFT]" wrote:
> 

[ Post a follow-up to this message ]

Hi Stefan, I dont want to appear rude and I do appreciate the help and
suggestions you have given me over the last few weeks but surely this is not
the point.

We are using map to host headers on the live site but not on dev (because of
the localhost issue  & because of the not dev tools supported issue).

What I am trying to find out is if we are really expected to install VS on
the live web server and change the "TemplateFile" property of the template i
n
the MCMS Template Explorer? This is necessary because the root IIS changes
from a VD in dev to a website in live...

Thanks

John

"Stefan [MSFT]" wrote:

> Hi Lta,
>
> the MCMS developer tools are not supported and do not work correct if the
> servername is different from "localhost".
>
> 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[/url...nyurl.com/8ugwj
> ----------------------
>
>
> "Lta" <Lta@discussions.microsoft.com> wrote in message
> news:F8473973-1A73-417D-98A6-6D09F957D57C@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi Lta,

actually it is highly recommended always to have the identical virtual
directory structure on all systems.
So never change the virtual directory structure between the dev and the live
site otherwise you have to adjust the "SourceFile" property of the template.

To adjust this property you don't have to install the developer tools or
VS.NET. A small console application using the CmsApplicationContext could do
the same.

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
----------------------


"Lta" <Lta@discussions.microsoft.com> wrote in message
news:9A0D0CC6-4180-4E7A-B027-44C3C321AA99@microsoft.com...[vbcol=seagreen]
> Hi Stefan, I dont want to appear rude and I do appreciate the help and
> suggestions you have given me over the last few weeks but surely this is
> not
> the point.
>
> We are using map to host headers on the live site but not on dev (because
> of
> the localhost issue  & because of the not dev tools supported issue).
>
> What I am trying to find out is if we are really expected to install VS on
> the live web server and change the "TemplateFile" property of the template
> in
> the MCMS Template Explorer? This is necessary because the root IIS changes
> from a VD in dev to a website in live...
>
> Thanks
>
> John
>
> "Stefan [MSFT]" wrote:
> 

[ Post a follow-up to this message ]

OK,

1. If I have an identicle virtual directory structure on the live site then
I cannot use map channels to host headers because virtual directories do not
have host headers.

2. If I have an identicle virtual directory structure in the live host
headered website on the live site I receive a CmsAuthorizationModule error
because the web.config file is being referenced in the website root and agai
n
in the LtaOnlineV2 virtual directory which references itself - required
because identicle VD to dev.

3. If we have to (I really don't want to because we cannot auto deploy new
templates) adjust the "TemplateFile" property (I don't think "SourceFile"
exists for an MCMS object) can we run the MCMS Template Explorer outside of
Visual Studio or or we need to build our own applet?

Thanks again,

John

"Stefan [MSFT]" wrote:

> Hi Lta,
>
> actually it is highly recommended always to have the identical virtual
> directory structure on all systems.
> So never change the virtual directory structure between the dev and the li
ve
> site otherwise you have to adjust the "SourceFile" property of the templat
e.
>
> To adjust this property you don't have to install the developer tools or
> VS.NET. A small console application using the CmsApplicationContext could 
do
> the same.
>
> 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[/url...nyurl.com/8ugwj
> ----------------------
>
>
> "Lta" <Lta@discussions.microsoft.com> wrote in message
> news:9A0D0CC6-4180-4E7A-B027-44C3C321AA99@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi John,

1) the virtual directory is completly independend from the Map channel to
host header name feature. There is no need to rename a virtual directory if
this feature is enabled.
Please explain in more detail why you are seeing an issue here.

2) no web.config should reside in the root of an MCMS website. It is
recommended to have all template projects in a web application below the
root. Then this problem will not occur.

3) actually there is no "TemplateFile" property. The property is named
"SourceFile".
The following tool is able to do this without VS.NET:
http://www.gotdotnet.com/Community/...1C-355569563507

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
----------------------


"Lta" <Lta@discussions.microsoft.com> wrote in message
news:ACF44B65-89D3-4B8D-B21E-6726B1C17C35@microsoft.com...[vbcol=seagreen]
> OK,
>
> 1. If I have an identicle virtual directory structure on the live site
> then
> I cannot use map channels to host headers because virtual directories do
> not
> have host headers.
>
> 2. If I have an identicle virtual directory structure in the live host
> headered website on the live site I receive a CmsAuthorizationModule error
> because the web.config file is being referenced in the website root and
> again
> in the LtaOnlineV2 virtual directory which references itself - required
> because identicle VD to dev.
>
> 3. If we have to (I really don't want to because we cannot auto deploy new
> templates) adjust the "TemplateFile" property (I don't think "SourceFile"
> exists for an MCMS object) can we run the MCMS Template Explorer outside
> of
> Visual Studio or or we need to build our own applet?
>
> Thanks again,
>
> John
>
> "Stefan [MSFT]" wrote:
> 

[ Post a follow-up to this message ]