I am fairly certain the .NET versioning (numbering release) scheme is the dumbest ever created. Seriously who in their right mind does a point release that is a extension of the previous point but not the one before that (2.0 -> 3.0)? Then 3.0 -> to 3.5? wtf? Remember 1.0 and 1.1? Hmmm. How does that fit in? Oh yea, it doesn’t.
It went like this…
1.0 to 1.1. Perfect. Basically the 1.0 framework fixed with a couple new things. That’s actually how it took place.
Then 2.0. A whole new framework. Yay! We are good at this point.
Then 3.0. Huh? Another new framework? Yay!? Wait, no, huh? It’s not a framework? It’s a extension but only for 2.0 and not related at all to 1.0 or 1.1? Oh good heavens MS.
Then 3.5 Another extension to 2.0 or actually 3.0? Ok, now I’m getting mad. What happened to 3.1, 3.2, etc.?
What’s next? 8.0 with 10.0 extentions?
Might as well number it 38.5. What’s the difference at this point? There is NO consistency anyway and the higher the number the better right?
Anyway here is the 2.0 -> 3.5 relationships…
Seriously, if you know what the hell MS was thinking, post a comment.
2 Comments
Leave a comment:
I feel your pain brother. I too thought “WTF” when I had finally become comfy with 2.0, and here comes 3.5!?!?!!? I completely missed 3.0 because I was nose down in work.
Crap, I still have clients on classic ASP!
Ha! Just noticed your animated gif up top. Nice. hahahaha
Yeah, I feel that way sometimes too…