Subsonic Vs NHibernate
What is the concensus on when to make use of among these devices adversed to the various other? I locate Subsonic really valuable in regards to obtaining points done promptly, yet on huge tasks it often tends not to range, and also its connections your domain name version to your data source version. That is where Nhibernate can be found in as it offers you light-weight POCOs that are unconnected to your data source version, yet the arrangement time is a lot longer.
I would certainly advise SubSonic if your task collaborates with the ActiveRecord sight that the database is your version. You'll get one class per table and also every little thing simply amazingly functions. You can certainly fine-tune and also bypass points, yet if you (or your task) basically differ with the class - per - table strategy, I would certainly consider NHibernate given that it begins with the extra intricate (yet extra adaptable) strategy of mapping your domain name version to your database.
If you are making use of a reasonably straightforward database that is under your control (as in, you can transform columns without sending out 8 kinds to a database department oversight testimonial board), I would certainly advise beginning with SubSonic and also relocating to NHibernate if SubSonic does not fulfill your demands.
I assume you virtually accomplished. Subsonic creates code, so your organisation things will certainly be reflective of your data source framework. nHibernate makes use of mapping documents which map your organisation challenge the data source so your things can be structured nonetheless you such as.
Just how huge of a task is this? Will there be lengthy term assistance required? Is the price performance of Subsonic mosting likely to counter any kind of possible scaling concerns?
Slightly off subject, yet in a comparable blood vessel. Have you considered Castle ActiveRecord it is created in addition to NHibernate and also gets rid of the demand to hang around developing XML mappings from code to the data source. Like NHibernate you can structure your domain name things as you desire and also later on create a data source schema from this framework.
Making use of ActiveWriter, an added device, you can conveniently map from your data source to domain name things.