found and displayed in this view.
- Nerd Dinner on Rails
Magazine/Issue: CoDe Magazine, 2010 May/Jun
Release Date: Friday, May 07, 2010
Quick ID: 1006071
It is often said that ASP.NET MVC was inspired by Rails. What better way to test that assertion than by writing the Nerd Dinner ASP.NET MVC application in Rails? In this article, I’ll take you through the steps I used to get Nerd Dinner up and running in Rails. A few points to keep in mind:
- A Practical Use of Indexers
Magazine/Issue: CoDe Magazine, 2010 Mar/Apr
Release Date: Friday, February 12, 2010
Quick ID: 1003121
Consider this hypothetical: You need to track different ways it is permissible to contact a customer.Or perhaps there are multiple attributes you wish to attach to an entity. Further, perhaps you want to define new attributes that can vary from entity to entity. From a database perspective, this can present a thorny problem. Fortunately, indexers in C# provide an elegant solution to the problem. In this article, I will show you how to use indexers to expand an organization’s data and at the same time, have minimal impact on an organization’s database structure. I will also show you how to incorporate this technique with NHibernate and how to verify your results with the MBUnit and TestDriven.net unit testing frameworks.
- Relational Database Persistence with NHibernate, Part 2
Magazine/Issue: CoDe Magazine, 2009 Jul/Aug
Release Date: Friday, June 26, 2009
Quick ID: 0907121
This article continues from the May/June 2009 issue of CODE Magazine (Quick ID 0906081) which covered why you want to use NHibernate, techniques for configuring NHibernate, how to map your objects to your data entities, and how to load basic objects.
- Relational Database Persistence with NHibernate, Part 1
Magazine/Issue: CoDe Magazine, 2009 May/Jun
Release Date: Monday, April 27, 2009
Quick ID: 0906081
Take advantage of the best relational databases and object-oriented design have to offer without compromising either.Using an object/relational mapping framework like NHibernate, you can significantly reduce the amount of code you write (and therefore potential bugs) for performing standard operations against your database and save the heavy ADO.NET coding for the complicated scenarios.