I would like to know how best to develop a solution with multiple ORMs.
Until now, all the projects that I have seen are strongly related to the choice of ORM, and they adhere to it until the end. Nhibernate, Castle ActiveRecord, Linq to SQL, WilsomORM, LLBLGen, SubSonic, Entity Framweork, others ...
I thought whether I should or not, to separate the strong attitude of this choice to the rest of the project. To some extent, I could change the ORM anytime I wanted.
At the moment, the only idea that I have something like a "factory" is returning an ORM object to me, and then I will attach it to some "internal" object.
There are situations when a project starts with some restrictions and decisions made at that time, it gives no choice but to select one specific ORM or another material in another area.
But later in time, months, a year or so, much will change, more funds, more support, technology advancement, new frameworks / ideas, etc ... will provide us with better options, and in this situation it will be really great, to be able to change the ORM without significant changes to the application (at this time it can be HUGE).
I would like to know your opinion.
Thanks guys.