NewsBot
1
I don't know if most of you still remember, but a couple of weeks ago, there's this debate about Microsoft*Distribution of*.Net 3.5 that's just too large to be distributed to client. Read it here*if you wish. After that discussion, it gets me to think on how .Net is distributed. Comparing with Java I found some questions that might be worthy of a discussion.
So, the first time .Net was first launched, we have this .Net 1.0 which marks the advent of the first generation of CLR and the .Net Framework Library 1.0. Shortly after, we have .Net 1.1 which delivers fixes and improvements over .Net 1.0. A couple of years later we have .Net 2.0 which includes major overhaul of the .Net Framework. What these three things have in common is that, they are delivered/distributed as a complete framework. Which means, that each framework can run on its own, without any dependancies with each other.
Along came Windows Vista which incorporates WPF, WF, InfoCard/CardSpace, WCF technologies. Microsoft decides to christined these into .Net Framework 3.0. And lately .Net Framework 3.5 which includes LINQ, further enhancements,*and Service Packs for .Net Framework 2.0, and 3.0 arrived (making it a huge bloat). But from what I understand is that .Net framework 3.0 and 3.5 are all runs on top of .Net Framework 2.0. (Well, 3.0 is on top 2.0, and 3.5 is on top of 3.0). With this setup, Microsoft warants everyone who wants to use .Net 3.5 to install .Net 2.0->.Net 3.5.
Now, my question is: if this is true, then what the future of .Net framework will be? will it follows this kind of trend? if there's a big overhaul in CLR 2.0, will we have .Net framework 4.0 or .Net Framework 2.0 SP2? Does that means CLR will never get updated pass version 2.0? And what about extra baggages? I can't use LINQ without installing WPF, WCF, CardSpace which really doesn't have any connection with LINQ at all? Will we ever have a complete independent framework again?
I understand that the concept of a 'whole' package is very important for maintainability, but maybe Microsoft had taken it a little bit too far? Of course I'd really hate to describe my system specification like: Java 1.5, Struts 1.2, XDoclet 1.3, Tomcat 1.4, JavaMail 1.2, etc, etc (which is totally confusing), but in the other way, I'd really like to be able to use LINQ without having to install WPF and CardSpace. And with current distribution scheme this is just not possible.
More...
View All Our Microsoft Related Feeds
So, the first time .Net was first launched, we have this .Net 1.0 which marks the advent of the first generation of CLR and the .Net Framework Library 1.0. Shortly after, we have .Net 1.1 which delivers fixes and improvements over .Net 1.0. A couple of years later we have .Net 2.0 which includes major overhaul of the .Net Framework. What these three things have in common is that, they are delivered/distributed as a complete framework. Which means, that each framework can run on its own, without any dependancies with each other.
Along came Windows Vista which incorporates WPF, WF, InfoCard/CardSpace, WCF technologies. Microsoft decides to christined these into .Net Framework 3.0. And lately .Net Framework 3.5 which includes LINQ, further enhancements,*and Service Packs for .Net Framework 2.0, and 3.0 arrived (making it a huge bloat). But from what I understand is that .Net framework 3.0 and 3.5 are all runs on top of .Net Framework 2.0. (Well, 3.0 is on top 2.0, and 3.5 is on top of 3.0). With this setup, Microsoft warants everyone who wants to use .Net 3.5 to install .Net 2.0->.Net 3.5.
Now, my question is: if this is true, then what the future of .Net framework will be? will it follows this kind of trend? if there's a big overhaul in CLR 2.0, will we have .Net framework 4.0 or .Net Framework 2.0 SP2? Does that means CLR will never get updated pass version 2.0? And what about extra baggages? I can't use LINQ without installing WPF, WCF, CardSpace which really doesn't have any connection with LINQ at all? Will we ever have a complete independent framework again?
I understand that the concept of a 'whole' package is very important for maintainability, but maybe Microsoft had taken it a little bit too far? Of course I'd really hate to describe my system specification like: Java 1.5, Struts 1.2, XDoclet 1.3, Tomcat 1.4, JavaMail 1.2, etc, etc (which is totally confusing), but in the other way, I'd really like to be able to use LINQ without having to install WPF and CardSpace. And with current distribution scheme this is just not possible.
More...
View All Our Microsoft Related Feeds