New Project Strategy: develop in 1.1 then migrate to 2.0 just before going live

[Jeff]

Looking for your highly subjective opinions (from those of you who have been
working extensively with VS 2005).

I have a client that needs/wants a complete rewrite of an existing
application. I will be proposing a .NET Windows application with a
supporting SQL Server database. It will likely take 4-5 months before we
roll out the first production version.

Because of the apparent issues with VS 2005 (poor performance, unpredictable
and generally buggy behaviour), I am thinking it might make sense to develop
this app in VS.NET 2003/.NET 1.1. Then, around the time we're ready to roll
out the first production version, migrate it to .NET 2.x just before going
live.

I say 2.x because Microsoft has plans to release a service pack for it
mid-way through 2006, so we might have a minor version number change at that
time. Also, it appears that the service pack from Microsoft, if released
mid-year, will stabilize things so we can [hopefully] have a smooth
transition to 2.x just before going live.

Does this strategy make sense? Thoughts? Opinions?

Thanks!

[Ray Cassick \(Home\)]

If the stability of 2005 is really an issue for you (I have not seen half
the issues that some people say there are) then I guess it is ok. I might
suggest that along the way, at each mini-milestone maybe, you run your code
through 2005 just to see if there is anything that crops up that you might
want to address. It might save you some issues when you are ready to do the
final move.

"Jeff" <[e-mail]> wrote in message
news:ez**************@TK2MSFTNGP15.phx.gbl...

Looking for your highly subjective opinions (from those of you who have
been working extensively with VS 2005).

I have a client that needs/wants a complete rewrite of an existing
application. I will be proposing a .NET Windows application with a
supporting SQL Server database. It will likely take 4-5 months before we
roll out the first production version.

Because of the apparent issues with VS 2005 (poor performance,
unpredictable and generally buggy behaviour), I am thinking it might make
sense to develop this app in VS.NET 2003/.NET 1.1. Then, around the time
we're ready to roll out the first production version, migrate it to .NET
2.x just before going live.

I say 2.x because Microsoft has plans to release a service pack for it
mid-way through 2006, so we might have a minor version number change at
that time. Also, it appears that the service pack from Microsoft, if
released mid-year, will stabilize things so we can [hopefully] have a
smooth transition to 2.x just before going live.

Does this strategy make sense? Thoughts? Opinions?

Thanks!