Group items tagged

"Model-View-Controller (MVC) is probably the most cited example of an architectural software pattern. It was conceived by Trygve Reenskaug working in the SmallTalk group at Xerox Parc in 1978. One motivation for the pattern was the separation of concerns: to allow Model objects to be concerned only with modeling business capabilities, not with how their data and methods were presented to the user, nor with capturing or responding directly to user inputs.[1] "

Alternative AJAX frontend for Asp.Net MVC applications

Simplify dynamic JavaScript UIs by applying the Model-View-View Model (MVVM) pattern.

"backbone.js from DocumentCloud is a small (2KB, packed) open-source library which allows you to apply the MVC (Model-View-Controller) principle to your JavaScript applications. Backbone supplies structure to JavaScript-heavy applications by providing models key-value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing application over a RESTful JSON interface."

" Naked Objects takes a domain object model, written as POCOs but following a few very simple conventions, and dynamically creates one or more complete user interfaces for it, using reflection (not 'code generation' or 'scaffolding'). It is highly effective in support of Domain-Driven Design, OO Modelling, and/or Agile Development. Naked Objects MVC builds upon the core framework to create a complete web-based user interface, using ASP.NET MVC 3. The generic user interface may be customised via the .CSS, by adding custom views, or custom controllers, as needed. Entity Framework is used to persist objects on a database. Security may be handled simply via Forms Authentication and attribute-based authorisation, or more comprehensively via Microsoft WIF and an STS. "

Great article about how modelbinding works in Asp.net MVC and how to write your own moderlbinders.

"Crazy random logo of evocative clipart combining the .NET Logo and some universal powerplugs into an unofficial logoI always like to remind folks of the equation ASP.NET > (ASP.NET MVC + ASP.NET WebForms). The whole "base of the pyramid" of ASP.NET has lots of things you can use in you applications. Some of these useful bits are Session State, Membership (Users), Roles, Profile data and the provider model that underlies it. Using these isn't for everyone but they are very useful for most applications, even ones as large as the ASP.NET site itself."

"In case you did not see the latest news, what we used to know as WCF Web API was recently rebranded and included in ASP.NET MVC 4 as ASP.NET Web API. While both frameworks are similar in essence with focus on HTTP, the latter was primarily designed for building HTTP services that don't typically require an user intervention. For example, some AJAX endpoints or a Web API for a mobile application. While you could use ASP.NET MVC for implementing those kind of services, that would require some extra work for implementing things right like content-negotiation, documentation, versioning, etc. What really matter is that both framework share many of the extensibility points like model binders, filters or routing to name a few."

In this article I will explain about IIS request processing and concept of worker process and application pool.

"The Model-View-Controller (MVC) pattern is an architectural design principle that separates the components of a Web application. This separation gives you more control over the individual parts of the application, which lets you more easily develop, modify, and test them."

"Many Web applications require a way to restrict access to some resources (such as specific pages) so that those resources are accessible only to authenticated users. The default Web application project template for ASP.NET MVC provides a controller, data models, and views that you can use to add ASP.NET forms authentication to your application. The built-in functionality lets users register, log on and off, and change their password. For many applications, this functionality provides a sufficient level of user authentication."

Lists the built-in attributes you can use on you model for validation

Yup. Used this a little before. Seems handy.

"Naked Objects MVC combines the power of the naked objects pattern with Microsoft's ASP.NET MVC 2 framework. Now you can take a POCO domain object model and turn it into a fully-functional web application in minutes, without writing a single line of user interface code. You can then customise the generic user interface by adding custom style sheets, custom views and custom controllers, following standard ASP.NET patterns."

Quickly and simply validate your credit card fields by adding this attribute to your POCO model class.

Handy to pass more than one model to a view