Experience in .NET programming model (Programming Model / Paradigm)

Original link: http://www.cnblogs.com/jamesleng/archive/2011/10/22/2217273.html

Different programming models often means different Mind or Metaphor, from the big perspective, can be obtained by different combinations of different categories:

Declarative vs Imperative;

Procedural Programming vs Functional Programming;

Structured Progarmming,OOP+AOP,Component Based,Service Oriented;

meta-programming vs ?;

 

.NET as a platform and programming model is mainly related to Language and Framework. Personally in terms of experience, .NET platform for more programming model really under a lot of "its essence, to its dregs," the effort. As we all know a little, meta-programming the entire .NET platform is a very fundamental characteristics, here mainly refers to Generics and Reflection.

 

Language will be made by the most representative of C # quite master of taste, but nicely maintained its minimalist style. C # belongs to the whole Imperative, to Procedural-based, local integration and the Declarative Functional elements. Of course, it belongs to OOP + AOP, but in practice, we really wrote a lot of OO code is not ye authentic, that is, Structured Programming or worse.

 

On the Framework, the programming model it contains very rich, can be said to be flourishing, colorful, on the whole belong Imperative, to Procedural main part belongs Declarative, belonging to the OOP + AOP + Component Based, part belongs to Service Oriented, the following is personal experience:

ADO.NET belong Imperative.

ASP.NET belong Declarative + Imperative. This field is divided into two kinds of WebForms and MVC programming model.

WPF belong Declarative + Imperative.

WCF belong Declarative + Imperative, belongs to Service Oriented. Due to uphold the concept of loose coupling, AOP everywhere, amazed.

WF belong Declarative + Imperative. Uphold its "Program Is Data" concept, there are meta-programming taste (here refers to DSL), opened a door for the DSL, in fact, one of the few fans DDD weapon.

EF belongs Declarative + Imperative. One of the basic weapon is the DDD fan favorite.

WindowsForms belong Imperative.

EnterpriseService belong Declarative + Imperative. Its essence is the COM + package a bit.

Reproduced in: https: //www.cnblogs.com/jamesleng/archive/2011/10/22/2217273.html

Guess you like

Origin blog.csdn.net/weixin_30896657/article/details/94786451