For desktop programmers, do you avoid deploying .NET 3.5 framework on client machines for this? If so, is this facility complete?
[edit]
The .NET 3.5 Framework reflects the OLE 2.0 (aka com) spirit. When 2.0 comes new, some users are asking if the wet version will be 3.0. But no one will have OLE 2.0 a solid architecture where all improvements can be made in the future without touching the underlying architecture.
I think that as a solid architecture in the CLR of the .NET Framework 2.0, there will be no need to change the underlying architecture to fulfill future improvements. .NET 3.5 was shipped without the need to change its underlying CLR (2.0). If Microsoft can improve the .NET (5.0) without making changes in the built-in architecture (CLR 2.0), then it is a proof that the introduction of CLR 2.0 is a solid foundation from the beginning.
That's not to say about JVM, its foundation is flawed. Their Generic can not get first class support from their VM / CLR.
It is being said, .NET 3.5 is the only additional library, where I do not need some functionality, something to me happily (eg, LINQBridge). The rest are just (not dependent on 3.5). To continue using VS 2008 still, you can target Net 2.0 (only 20 MB), still can get clean features: lambda, extension methods, estimated variables, anonymous types, automatic properties, e.t.c. I use LINQBridge because we have some PCs that our users use on Win2k,
Therefore no one 3.5 is not supported. I think IEnumberable stuff is excellent, and its performance is similar to Microsoft. This whole IQueryable thing is missing, though, and I do not think there are excelment stuff or LINQ-TO-SQL stuff.
Comments
Post a Comment