Is the .Net 4 Framework going to change before the "go-live" or can we safely assume that the framework will stay the same as it currently is in the Release Candidate?
+6
A:
I would be surprised to see any significant new features or API changes - but I'd expect some bug fixes or performance improvements. To put it another way, I would still put any software you're building through a fairly rigorous test run after the release, but with the expectation of it still working.
Jon Skeet
2010-03-17 15:40:01
So, installing the latest .Net 4 framework on a server is not an advisable idea, at the moment?
Ardman
2010-03-17 15:45:16
If you're looking to install it as a test, that would probably be ok. .NET 4 is a new .NET set and not an add-on like 3.0 and 3.5 were to 2.0, so it "shouldn't" interefere with existing .Net architecture. However, i wouldn't put it on any mission critical or high-availability servers just yet, nor would I make any production processes reliant on 4 until the final release.
BBlake
2010-03-17 15:59:27
+1. Great, thanks for that info.
Ardman
2010-03-17 16:03:07
A:
Assume stability. At this point, significant changes would have to be rooted in a design desaster. You basically talk of fixing critical issues at this point. Even IF the api changes, it is going to be minimal.
TomTom
2010-03-17 15:40:39
+5
A:
You said it yourself - Release Candidate. This means that though large changes are unlikely, they can occur as can small changes.
Oded
2010-03-17 15:40:52
+1
A:
Framework 4.0 (and VS 2010) release candidate is available under a Go Live license which, amongst othre things, includes "committed to providing a smooth upgrade path from Beta 2 to RC and then to the final release (“RTM”) of Visual Studio 2010 and the .NET Framework 4" and providing support should things go wrong.
Meaning - the API might change (unlikely) and if it does, and it causes big issues, you can enlist MS Support to help.
All things going to plan it should be very smooth to start using RC now and move to RTM when required.
Michael Shimmins
2010-03-17 22:37:44
Also - maybe a point of interest - we're using RC as our devleopment platform for a project that is scheduled to be released a few months after RTM. We feel the risk/reward ratio was worth it.
Michael Shimmins
2010-03-17 22:41:08