Hello,

I am about to start on a new MCMS 2002/ ASP.NET 2 project for a client, with
the first phase being about 8 weeks development work with the probablilty of
extra phases being added on afterwards.

Now I know the next release of MCMS is being made part of MOSS 2007 so I'd
much rather build using that, but it isn't released yet, so I am stuck with
MCMS 2002 for now (the client would never let us build using a BETA).

My questions are to do with future proofing my development so I could
convert to MOSS 2007 when its released (and considered stable).

So here are my questions...

1. MCMS is costing my client around $5000. I suspect that Microsoft will not
have released pricing of MOSS 2007 yet, but does anyone have any ballpark
figures for this (Is it likely to be in the same region as MCMS or are we
talking hundreds of thousands here)?

2 If we upgrade when the time is right, is it likely that the client will
have to purchase MOSS 2007 on TOP of the cost of MCMS that they will have
already forked out for, or is there likely to be an upgrade path from MCMS t
o
MOSS 2007?

3. In my development now, is there anything I should be doing to make the
conversion from MCMS to MOSS 2007 a smoother process? Any known issues with
the conversion process that makes you wish "Why didnt I build it this way
instead of that way?"

I can't help thinking that I'm starting development of this project at
exactly the wrong time, but we have our deadlines, and I dont see any other
options at present.

Thanks for your help.

Richard

[ Post a follow-up to this message ]

anyone?

"Richard" wrote:

> Hello,
>
> I am about to start on a new MCMS 2002/ ASP.NET 2 project for a client, wi
th
> the first phase being about 8 weeks development work with the probablilty 
of
> extra phases being added on afterwards.
>
> Now I know the next release of MCMS is being made part of MOSS 2007 so I'd
> much rather build using that, but it isn't released yet, so I am stuck wit
h
> MCMS 2002 for now (the client would never let us build using a BETA).
>
> My questions are to do with future proofing my development so I could
> convert to MOSS 2007 when its released (and considered stable).
>
> So here are my questions...
>
> 1. MCMS is costing my client around $5000. I suspect that Microsoft will n
ot
> have released pricing of MOSS 2007 yet, but does anyone have any ballpark
> figures for this (Is it likely to be in the same region as MCMS or are we
> talking hundreds of thousands here)?
>
> 2 If we upgrade when the time is right, is it likely that the client will
> have to purchase MOSS 2007 on TOP of the cost of MCMS that they will have
> already forked out for, or is there likely to be an upgrade path from MCMS
 to
> MOSS 2007?
>
> 3. In my development now, is there anything I should be doing to make the
> conversion from MCMS to MOSS 2007 a smoother process? Any known issues wit
h
> the conversion process that makes you wish "Why didnt I build it this way
> instead of that way?"
>
> I can't help thinking that I'm starting development of this project at
> exactly the wrong time, but we have our deadlines, and I dont see any othe
r
> options at present.
>
> Thanks for your help.
>
> Richard

[ Post a follow-up to this message ]