Start or not?

[Snake]

Will my ASP.NET 2.0 Beta2 application work correctly on .NET 2.0 release?

Will my ASP.NET 1.1 work correctly on .NET 2.0 release?

Thanks.

Btw I ask this because we would like to start production of a large system
hich should not seize working after beta 2 -> release update.

 

[Jon Skeet [C# MVP]]

Will my ASP.NET 2.0 Beta2 application work correctly on .NET 2.0 release?

Not necessarily. It's almost inevitable that some things change between
a beta and a release. Whether your application uses that or not, I
don't know...

Will my ASP.NET 1.1 work correctly on .NET 2.0 release?

That's much more likely - although again I wouldn't be surprised if a
*few* things have been broken.

Btw I ask this because we would like to start production of a large system
hich should not seize working after beta 2 -> release update.

Well, there's only two weeks to wait before v2 is released. So long as
you've got a good test system in place to find out where things have
been broken, you should be okay - but don't deploy the released 2.0
assuming that nothing will break.

 

[S.M. Altaf [MVP]]

Logic and common sense dictate that you should NOT start major production work on a beta, no matter how "reliable" you are told it is. You know full well that the Beta will be out soon, so it's best that you either wait for that, or just use the 1.1 framework.

Working on a beta is like jumping from the top of a staircase hoping that the last few stairs are made of jello.

-Altaf
[MVP]


--------------------------------------------------------------------------------

All that glitters has a high refractive index.
www.mendhak.com

Will my ASP.NET 2.0 Beta2 application work correctly on .NET 2.0 release?

Not necessarily. It's almost inevitable that some things change between
a beta and a release. Whether your application uses that or not, I
don't know...

Will my ASP.NET 1.1 work correctly on .NET 2.0 release?

That's much more likely - although again I wouldn't be surprised if a
*few* things have been broken.

Btw I ask this because we would like to start production of a large system
hich should not seize working after beta 2 -> release update.

Well, there's only two weeks to wait before v2 is released. So long as
you've got a good test system in place to find out where things have
been broken, you should be okay - but don't deploy the released 2.0
assuming that nothing will break.

 

[Jon Skeet [C# MVP]]

Logic and common sense dictate that you should NOT start major
production work on a beta, no matter how "reliable" you are told it
is. You know full well that the Beta will be out soon, so it's best
that you either wait for that, or just use the 1.1 framework.

Working on a beta is like jumping from the top of a staircase hoping
that the last few stairs are made of jello.

I would have no problems starting a new project on 2.0 at this point,
given that it will be out very soon.

I wouldn't put it on a production server, and I would have heavy
testing ready to make sure that I can catch the changes - but I don't
see that it's any more risky to start work on it now than it would be
in a couple of weeks. You need tests to tell you whether it works or
not, right? Those tests will still work in a fortnight...