Dotnet server-side framework from mastery to abandoned pits

When you see this experience sharing, I've moved the server-side main power to Java.

Pure as a souvenir.

The other part of the implementation of the oauth2.0 is not written, because the particularity is too strong, completely according to the needs of their own combined with its concept of rewriting.

Why would I choose Spring.net and NHibernate?

So, did EF have a stable version of Poco,ef in that era? Just come out, but the architecture design can't wait.

EF Support Poco When the time, see the next transaction management is not, that is, to rely on the windows underlying things, the main idea can not accept, that will be enterprise Application architecture design is Java books.

Then Microsoft came out of code first with CQRS or something tied together, or Microsoft bundled thinking.

I believe that the future even if the small partners to the core, a lot of thinking needs to break through, this is the difference between Microsoft thought and Linux ideas, but also can not blame Microsoft, the history of legacy issues.

Why haven't I updated my blog for years?

Because there is a fault in the. NET technical knowledge structure, when I break through, I find that another community on these so-called "high-end problems" is a common occurrence, then I have what good to publish, this time also need to quickly absorb is.

Later looked at the next Liu Dong. NET blog, found that the same, a few years there is nothing good to publish, and then suddenly updated a lot of spring.net integration strategy, and finally moved to Java, the history of a surprisingly similar.

Then I this integration strategy based on Liu Dong. NET, the integration of some new things, more nhibernate related improvements, but also just put some components or release some examples, the time relationship did not write a specific strategy, but also need to be interested in the small partner to collect information.

In addition, the following are all after the actual baptism, please rest assured to browse.

Dotnet server-side framework from mastery to abandoned pits