Effort/Time in migrating 1.1 to 2.0

[Kyong Kwak]

Hi, wanted to know what people have experienced in terms of effort+time in
migrating your apps to 2.0 from 1.1?

Are there any case studies on msdn? I couldn't find any..

how well did it go with you all? days? weeks? months?
we have a mid sized external app using mcms, a small asp.net app for internal
use, a small console app, and a webservice..

we will migrate if it's a relatively small investment.. otherwise, we will
stick with 1.1 for at least a year more as we have lots of integration projects
coming up.. my idea is that upgrading now will be cheaper than doing the
upgrade AFTER making the apps larger.. but that's me..

thank you

 

[Greg Young]

It really depends on your code and how much you wish to take advantage of
the new features.

I will default to someone else on the mcms app ...

Your web app, I would count on throwing away the presentation tier.
The web service and console app should be hours (as they sound like they do
not have much code .. you may even consider moving the webservice directly
to WCF)

Cheers,

Greg Young

 

[Kevin Yu [MSFT]]

Hi Kyong,

Yes, it really depends on your current app. For ASP.NET migration, here is
a good document for your reference:

http://msdn2.microsoft.com/en-us/library/ms228097.aspx

Kevin Yu
Microsoft Online Community Support

============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

 

[Carl Daniel [VC++ MVP]]

Hi, wanted to know what people have experienced in terms of
effort+time in migrating your apps to 2.0 from 1.1?

Are there any case studies on msdn? I couldn't find any..

how well did it go with you all? days? weeks? months?
we have a mid sized external app using mcms, a small asp.net app for
internal use, a small console app, and a webservice..

we will migrate if it's a relatively small investment.. otherwise,
we will stick with 1.1 for at least a year more as we have lots of
integration projects coming up.. my idea is that upgrading now will
be cheaper than doing the upgrade AFTER making the apps larger.. but
that's me..

I've tried migrating a couple project.

1. A large class library with about 1400 classes. The project conversion
worked flawlessly, and other than 50 or so deprecation warnings, everything
ported over without a hitch.

2. A large ASP.NET web project with about 400 pages. After multiple days of
trying to get the project ported to 2.0, we gave up. There's supposed to be
a new project type in VS2005 SP1 that will make porting 1.x ASP.NET projects
much easier. The ASP.NET project model changed significantly - for the
better - in 2005. The new feature in SP1 basically adds support for the 1.x
project model.

YMMV - ours certainly did.

-cd

 

[Kyong Kwak]

thanks greg and carl..

It was coded poorly and much of the logic reside in the code-behind.. if
we lose the presentation layer.. well that's bulk of the logic too.. sounds
like I won't have much leverage in convincing anyone to move to 2.0 at this
time.. we will move at some point, but not this year..

thanks a bunch!