Where to go for F4-view framework 4.0

Framework 4.0 CTP has been released for more than a month. During this period, I will try it out and try this new stuff. The general feeling is that Microsoft's technology is booming, and a lot of stuff has been inserted into F4. some are really good, but some still feel a little rough and cannot withstand the practical test. I will share this new framework with you to discuss the future of F4.

F1.1 is actually a test product ,. net Framework has actually matured since F2, and later F3 and f3.5 are actually extensions Based on F2. I personally think it should be defined as f2.1 and f2.2. I did not expect that Microsoft would like to make great strides and just add something to change to a new version.

In addition to fixing F2 bugs, F3 + f3sp1 mainly incorporates a 3w framework, including WPF, WCF, and WWF.
F3.5 and F3 are similar. Apart from fixing previous bugs, major extensions include: LINQ, WF, WCF, and add-in (which will be replaced by MEF in the future)
F3.5sp1 adds several new things: MVC, dynamic data, Entity Framework, data services, etc.

Of course, we can't ignore the language improvement of F3, such as the use of LINQ, lambda, extended functions, and VAR types.

But to be honest, it is really in the real project .. Except for C #, I have used almost none of the other w components except for WCF. Even when I was very interested in LINQ-to-SQL for a period of time, the results suddenly lost, And the ADO. NET development team was not planning to develop .. It immediately cooled my mind down. So F3 and f3.5 are in my eyes .. In fact, it is nothing practical to add a large batch of stuff ..

Let's see what F4 has brought to us? Let's take a look at Microsoft's new blueprint for F4:

After comparing the f3.5 blueprint, we can find the new things added in 4.0: velocity, Dynamic Language, MEF, parallel extensions.

Velocity:

This is a distributed cache solution provided by Microsoft. It already has the CTP version. I have read Terry Lee's introduction to velocity before. The general feeling is that it is easy to use. Because I have been using memcached for the past, and memcached has been tested by a large website like Facebook and is compatible with various platforms. So Microsoft wants to deal with memcached through velocity, and I feel that it is still a long way to go.

However, I found that velocity has a tag function, which is very useful for Batch Key cleaning. It is a highlight of velocity. Of course, memcached batch cleanup can also be implemented if it is encapsulated on the client. For details, refer to the introduction of the memcached section in my essay. Hey, make a small advertisement.

Dynamic Language:

If you trace back to Microsoft's most popular dynamic language, it should be regarded as ASP, but after coming out of. net, Microsoft is on the old path .. Re-compile the DLL for each update .. So annoying. Traditional languages have insufficient support for concurrency and expansion.ProgramMany factors, such as high quality requirements and low development efficiency, force some people to review other programming patterns, such as Erlang, Python, and Ruby. F #, ironpython, ironruby, and other dynamic languages are added to F4, which should be an important step for F4. In terms of feelings, ironpython is my most supported. After all, it was so nice to use Python before. Haha. If I can use python on. NET, it would be a perfect thing. However, I guess Microsoft is still counting on F # as the main product of DL. After a brief introduction, I feel that he is doing well in terms of concise language, encapsulation, and ease of use. However, after all, it is a new language. Just like C # in the past, it also takes a long time to test. I hope F # Will be better along the way.

MEF:

To be honest, I don't know what MEF is positioned. If the positioning is a DI/IOC container, the Enterprise Library or castle has implemented it. Why bother with another solution? Later, I carefully reviewed some documents and learned that MEF has a new feature, that is, implementing di operations through contract and further decoupling to some extent. It is estimated that MEF will act as a brute-force interface in this respect and will be better able in future versions. In a word, don't use a DI/IOC container to fool us.

Parallel extensions:

Good stuff ~ This is something I have always dreamed of. In particular, the machines are all multi-core. If I write a program and cannot fully utilize the performance of the multi-core, it's really amazing, I bought so many CPUs. However, the CTP version is still relatively simple for parallel operations and needs to be enhanced in terms of data synchronization. We hope that later versions will bring us more surprises.

Of course, in addition to new things, F4 has also made improvements to many components, such as MVC, Entity Framework, and LINQ-to-SQL (although the blueprint is included in LTS, but the final list of the 18 most popular F4 users should be observed), Asp. net Ajax, dynamic data, WPF, and so on. The sky is full of eyes .. However, the number of items in it is exactly the same, and it remains to be investigated ..

Overall, the new things brought by F4. However, we also remind you that not all things are good. Some things look beautiful, but they are not very good. So we still need to observe F4. The above is just the experience of the author, and it is not correct. please correct me more.

ArticleReprinted from: http://it.dianping.com/framework_4_overview.htm