Hi,

I have been developing a CMS site on Developer Edition.

The dev setup had the woodgrove .Net sample, and I developed my site along
side it - both off of the root channel.

I used host header mapping to get to the right channel.

Now I am deploying to a Std Edtion MCMS, obviously the host header mapping
won't work.

Am I correct in thinking Std Edition will effectively shift the channels up
one?

How should one develop multiple CMS sites on Developer Edition, but deploy
them on separate Std Editions?

Thanks
Martin

[ Post a follow-up to this message ]

Hi Martin,

that is one of the reasons that standard edition is cheaper than enterprise
edition: standard edition does not support multiple sites.
What you can do is to map different host headers to different IIS sites and
then add a default.aspx files in the root of each site that redirects to a
different channel.

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:ehlwIzOHGHA.3728@tk2msftngp13.phx.gbl...
> Hi,
>
> I have been developing a CMS site on Developer Edition.
>
> The dev setup had the woodgrove .Net sample, and I developed my site along
> side it - both off of the root channel.
>
> I used host header mapping to get to the right channel.
>
> Now I am deploying to a Std Edtion MCMS, obviously the host header mapping
> won't work.
>
> Am I correct in thinking Std Edition will effectively shift the channels
> up one?
>
> How should one develop multiple CMS sites on Developer Edition, but deploy
> them on separate Std Editions?
>
> Thanks
> Martin
>
>

[ Post a follow-up to this message ]

Hi Stefan,

Thanks for your answer.

I'll have to see how it works out when I deploy the site.  I believe I
need/want to go from a channel structure like:

DevEd channel structure
\Channels
\Channels\site1
...
\Channels\site2
\Channels\site2\ch1
\Channels\site2\ch2


to
StdEd channel structure
\Channels
\Channels\ch1
\Channels\ch2

If I'm right, there are two issues that need addressing
1) Hopefully the SiteManager Import/Export process facilitates the channel
movement.  Can you confirm?
2) I would need to change my channel navigation controls to account for the
channel structure change (not a problem).

If the channel structure doesn't change as I expect, then users would be
able to enter a url like
http://host/site2 which they wouldn't on the Dev Edition, and I wouldn't
want them to.

Thanks again
Martin



"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:udhFb9QHGHA.1032@TK2MSFTNGP15.phx.gbl...
> Hi Martin,
>
> that is one of the reasons that standard edition is cheaper than
> enterprise edition: standard edition does not support multiple sites.
> What you can do is to map different host headers to different IIS sites
> and then add a default.aspx files in the root of each site that redirects
> to a different channel.
>
> 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:ehlwIzOHGHA.3728@tk2msftngp13.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Hi Martin,

it is not possible to change the channel structure with export / import.
You need to adjust the structure either before export or after import.

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:etJcyQbHGHA.2012@TK2MSFTNGP14.phx.gbl...
> Hi Stefan,
>
> Thanks for your answer.
>
> I'll have to see how it works out when I deploy the site.  I believe I
> need/want to go from a channel structure like:
>
> DevEd channel structure
> \Channels
> \Channels\site1
> ...
> \Channels\site2
> \Channels\site2\ch1
> \Channels\site2\ch2
>
>
> to
> StdEd channel structure
> \Channels
> \Channels\ch1
> \Channels\ch2
>
> If I'm right, there are two issues that need addressing
> 1) Hopefully the SiteManager Import/Export process facilitates the channel
> movement.  Can you confirm?
> 2) I would need to change my channel navigation controls to account for
> the channel structure change (not a problem).
>
> If the channel structure doesn't change as I expect, then users would be
> able to enter a url like
> http://host/site2 which they wouldn't on the Dev Edition, and I wouldn't
> want them to.
>
> Thanks again
> Martin
>
>
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:udhFb9QHGHA.1032@TK2MSFTNGP15.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Hi Stefan,

I found that if I start the export at channel children, they get imported at
the root of the destination server.
So following the example below, if I export ch1, ch2 directly, not by
selecting site2, when I import, I get the channel structure I want.

I'm not completely home and dry, as I haven't got the site operating yet,
but it looks promising.

I now have to make my navigation controls cope with both channel structures.
Is there a programmatic way of getting the site root, that deals with
optionally having host header mapping?

I recall when I tried using RootChannel months ago, I had some wierd bug
that I had to work round, and ended up avoiding that property altogether.
(I'm was using sp1a., and still am)


Thanks
Martin

"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:eLc8d5$HGHA.3700@TK2MSFTNGP15.phx.gbl...
> Hi Martin,
>
> it is not possible to change the channel structure with export / import.
> You need to adjust the structure either before export or after import.
>
> 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:etJcyQbHGHA.2012@TK2MSFTNGP14.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Hi Martin,

your are using a side effect of the site deployment API when the parent of
an imported item is not available.
Then the item will be stored in a default location.
Be aware that the default location is different for Site Manager,
client-side SDAPI and server-side SDAPI.
In Site Manager you are able to configure the default location, in server
side SDAPI it is the root channel and in client-side SDAPI it is a special
channel which will be created.

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:OR3xYvDIGHA.2300@TK2MSFTNGP15.phx.gbl...
> Hi Stefan,
>
> I found that if I start the export at channel children, they get imported
> at the root of the destination server.
> So following the example below, if I export ch1, ch2 directly, not by
> selecting site2, when I import, I get the channel structure I want.
>
> I'm not completely home and dry, as I haven't got the site operating yet,
> but it looks promising.
>
> I now have to make my navigation controls cope with both channel
> structures. Is there a programmatic way of getting the site root, that
> deals with optionally having host header mapping?
>
> I recall when I tried using RootChannel months ago, I had some wierd bug
> that I had to work round, and ended up avoiding that property altogether.
> (I'm was using sp1a., and still am)
>
>
> Thanks
> Martin
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:eLc8d5$HGHA.3700@TK2MSFTNGP15.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Hi Stefan,

If I only plan to use Site Manager for deploying, I don't need to worry - do
I?

I didn't realise there were distinct SDAPIs for client and server side.
Where can I find out more about them?
Is the client SDAPI exposed by Site Manager, and the server SDAPI exposed by
MCMS website?

Thanks
Martin

"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:eJWzF3LIGHA.528@TK2MSFTNGP12.phx.gbl...
> Hi Martin,
>
> your are using a side effect of the site deployment API when the parent of
> an imported item is not available.
> Then the item will be stored in a default location.
> Be aware that the default location is different for Site Manager,
> client-side SDAPI and server-side SDAPI.
> In Site Manager you are able to configure the default location, in server
> side SDAPI it is the root channel and in client-side SDAPI it is a special
> channel which will be created.
>
> 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:OR3xYvDIGHA.2300@TK2MSFTNGP15.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Hi Martin,

the SDAPI is explained in detail in the MCMS documenation.
Ready to use sample code is included in the reference section of the
documentation.

The client site SDAPI requires Site Manager to be installed but the
functionality is not provided by Site Manager. but client side SDAPI and
Site Manager use the same underlaying COM componts for this.

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:Op$2CMQIGHA.2628@TK2MSFTNGP15.phx.gbl...
> Hi Stefan,
>
> If I only plan to use Site Manager for deploying, I don't need to worry -
> do I?
>
> I didn't realise there were distinct SDAPIs for client and server side.
> Where can I find out more about them?
> Is the client SDAPI exposed by Site Manager, and the server SDAPI exposed
> by MCMS website?
>
> Thanks
> Martin
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:eJWzF3LIGHA.528@TK2MSFTNGP12.phx.gbl... 
>
>

[ Post a follow-up to this message ]