The ASP.NET MVC Framework enables you to use any data access pattern or framework you want in order to retrieve and manage your models. If you want to use ADO.NET DataSets/DataReaders (or abstractions built on top of them) you can. If you prefer to use an object relational mapper (ORM) like NHibernate, LLBLGen, WilsonORMapper, LINQ to SQL/LINQ to Entities you can absolutely use those as well.
For our e-commerce sample application I'm going to use the built-in LINQ to SQL ORM shipped in .NET 3.5 and VS 2008. You can learn more about LINQ to SQL from my ongoing blog tutorial series that covers it (in particular make sure to check out my Part1, Part2, Part3 and Part4 posts).
Mapping URL Parameters to Controller Action Methods
This blog is a knowledge base...where I clip cool tricks and urls
MVC in ASP.NET part 2
Posted by breezback
- diving into LINQ
- clean CSS separation
- MVC in ASP.NET part 2
- MVC in ASP.NET
- Avoid Loops in Excel
- LINQ need primary key
- convert with generics
- BBuilder - Open source batch builder
- GridView DataBind LINQ to ASP.NET controls
- ASP.NET MVC
- Tuning Performance - LINQ to SQL
- LINQ Overview
- Local database sdf in VS2008
- Introduction to LINQ
- WPF. Draggable objects and simple shape connectors...
- linq book
- Open Source Batch Editor
- ▼ November (18)