|
Home > Archive > Microsoft Content Management Server > January 2007 > MCSM application with asp.net 2.0
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
MCSM application with asp.net 2.0
|
|
| bhagyashree74@gmail.com 2007-01-18, 7:19 pm |
| Hi all,
I have read in the older posts that to be able to use asp.net 2.0/VS
2005 features with MCMS 2002 SP1a, one must apply SP2 to MCSM. I have a
mandate to upgare my application build over MCMS to asp.net 2.0.
Can anybody suggest the methodology/steps that should be followed. Can
I use VS 2005 migration assistant to do the job after making the CMS
virtual directory hidden? Or one has to create every aspx/control
newly?
The help available on the web talks about SP2 upgradation.
Are these steps correct?
1. Take backup
2. Install SP2
3. Open the solution in VS 2005, allow conversion wizard to port the
solution, make note of errors
4. Resolve the errors pointed out by wizard. (VS 2005 requires XHTML,
IE web controls could conflict with System.Web.UI.Controls etc)
5. Compile the solution and test it
Is this correct approach?
Any help will be appreciated
Regards,
Bhagyashree
| |
| Stefan Goßner [MSFT] 2007-01-19, 7:19 am |
| Hi Bhagyashree,
you cannot covert the project using VS.NET.
It will then no longer be an MCMS template project.
You would need to create a new MCMS Web application project and convert the
templates one by one manually.
Or you can try to convert it automatically and then copy the migrated
templates into the new created MCMS web applicaiton.
Cheers,
Stefan
<bhagyashree74@gmail.com> wrote in message
news:1169166583.087624.102140@l53g2000cwa.googlegroups.com...
> Hi all,
> I have read in the older posts that to be able to use asp.net 2.0/VS
> 2005 features with MCMS 2002 SP1a, one must apply SP2 to MCSM. I have a
> mandate to upgare my application build over MCMS to asp.net 2.0.
> Can anybody suggest the methodology/steps that should be followed. Can
> I use VS 2005 migration assistant to do the job after making the CMS
> virtual directory hidden? Or one has to create every aspx/control
> newly?
>
> The help available on the web talks about SP2 upgradation.
>
> Are these steps correct?
> 1. Take backup
> 2. Install SP2
> 3. Open the solution in VS 2005, allow conversion wizard to port the
> solution, make note of errors
> 4. Resolve the errors pointed out by wizard. (VS 2005 requires XHTML,
> IE web controls could conflict with System.Web.UI.Controls etc)
> 5. Compile the solution and test it
>
> Is this correct approach?
>
> Any help will be appreciated
> Regards,
> Bhagyashree
>
| |
| Shady Khorshed 2007-01-22, 1:15 pm |
| Hi Bhagyashree,
please try this
http://shadiesm.blogspot.com/2007/0...service_22.html
Regards,
Shady Khorshed
"Stefan Goßner [MSFT]" <stefang@online.microsoft.com> wrote in message
news:ehqlCT6OHHA.3544@TK2MSFTNGP03.phx.gbl...
> Hi Bhagyashree,
>
> you cannot covert the project using VS.NET.
> It will then no longer be an MCMS template project.
>
> You would need to create a new MCMS Web application project and convert
the
> templates one by one manually.
> Or you can try to convert it automatically and then copy the migrated
> templates into the new created MCMS web applicaiton.
>
> Cheers,
> Stefan
>
>
> <bhagyashree74@gmail.com> wrote in message
> news:1169166583.087624.102140@l53g2000cwa.googlegroups.com...
>
>
|
|
|
|
|