Naked Objects for .NET

Naked Objects for .NET or Naked Objects MVC is a software framework that builds upon the <a href="/facts/ASP.NET_MVC/KFyeWXHx">ASP.NET MVC</a> framework.
As the name suggests, the framework synthesizes two <a href="/facts/Architectural_pattern/GnN0z06K">architectural patterns</a>: <a href="/facts/Naked_objects/1A2JQVYt">naked objects</a> and <a href="/facts/Model%E2%80%93view%E2%80%93controller/vRbMXjMm">model–view–controller</a> (MVC). These two patterns have been considered as antithetical. However, <a href="/facts/Trygve_Reenskaug/NC8fJ4SI">Trygve Reenskaug</a> (the inventor of the MVC pattern) has made it clear that he does not see it that way, in his foreword to Richard Pawson's PhD thesis on the Naked Objects pattern.
The Naked Objects MVC framework will take a <a href="/facts/Domain_model/rSxm7s5a">domain model</a> (written as <a href="/facts/Plain_Old_CLR_Object/tK20Xs8V">Plain Old CLR Objects</a>) and render it as a complete <a href="/facts/HTML/sSc3fT78">HTML</a> application without the need for writing any <a href="/facts/User_interface/e9sPEWVD">user interface</a> code - by means of a small set of generic View and Controller classes. The framework uses <a href="/facts/Reflection_(computer_programming)/Nj8stFfp">reflection</a> rather than <a href="/facts/Automatic_programming/zrrwX3CW">code generation</a>.
The developer may then choose to create customised Views and/or Controllers, using standard ASP.NET MVC patterns, for use where the generic user interface is not suitable.

Naked Objects for .NET open-in-new

Naked Objects for .NET