Group items tagged

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

Yup. Used this a little before. Seems handy.

Is there a way you can rate these links. I.e. which were most helpful?

I'll delete the ones that sucked and also perhaps flag the useful ones with a Like click

That sounds like a good plan. Tnx. :)

This link helped me the most in terms of figuring out how to implement jQuery validation with MVC. It includes a sample app that is very useful.

Thanx. Will check it out.

"Due to popular demand, here is a tutorial on how I created one of the more complicated pieces of machinery on my new site: the contact form. A lot of different techniques went into this"

I'm not the one that thinks so. Everyone else decided on that :D

EVERYONE!? That's a bit arrogant. Even for you. :P

Using Visual Studio symbols and source files makes debugging much easier. I am specially happy about ASP.NET MVC 2 source files because I develop on ASP.NET MVC 2 almost every day. You may also find other useful symbols and source files. In this posting I will show you how to get ASP.NET MVC source to your computer and how to use it.

Looks like I'll be using this one. Seems to be a bit better documented.

A Versatile and Expandable jQuery Plotting Plugin

One of the things my team has been working on has been a new view engine option for ASP.NET. ASP.NET MVC has always supported the concept of "view engines" - which are the pluggable modules that implement different template syntax options. The "default" view engine for ASP.NET MVC today uses the same .aspx/.ascx/.master file templates as ASP.NET Web Forms. Other popular ASP.NET MVC view engines used today include Spark and NHaml. The new view-engine option we've been working on is optimized around HTML generation using a code-focused templating approach. The codename for this new view engine is "Razor", and we'll be shipping the first public beta of it shortly.

"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] "

"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.

"If you are interested in the formal arguments for the Naked Objects pattern, and a scientific analysis of its benefits, read Richard Pawson's PhD thesis."

"A lot has been written about how to get ASP.NET MVC running on IIS 6 with extensionless URLs. Up until now, the story hasn't been very pretty. When running ASP.NET MVC on ASP.NET 4, it gets a lot easier."

"Now, I will show one real-world example which you may use it in your daily work of developing applications with ASP.NET MVC and jQuery."

"I'm excited to announce the release today of several products: * ASP.NET MVC 3 * NuGet * IIS Express 7.5 * SQL Server Compact Edition 4 * Web Deploy and Web Farm Framework 2.0 * Orchard 1.0 * WebMatrix 1.0 "