Persistence ignorance is typically defined as the ability to persist & retrieve standard .NET objects (or POCOs if you really insist on giving them a name). And a seemingly well accepted definitio
I\'m using Compact Framework 3.5 and have tentatively settled on a custom build of Subsonic 3.0 to do data access. The trouble is that I am used to developing model-first but am also interested in kee
I am just at the brink of going \"Ah HA!\" when it comes to coding Domain Driven Design.The question is How and where to define a MVC ActionMethod parameter class that involves an entity, a value obje
Our organization is looking to standardize on Entity Framework once v4 comes out. As a result, I am looking at what it would take to migrate our application that uses NHibernate for persistence to EF4
So I\'m quite new to C++, I\'ve basically been coding it all semester for a class. For our final project, we made an email client in C++ with .NET, and to do all the email sending and receiving, we we
i\'m under the impression that EF with POCO: allows you to map your own POCO\'s to the entities on the model (.edmx).
Alright, so this is absolutely killing me... If anyone could help me, I would be the happiest man on the face of the earth...
with my Repository classes, I use LinqToSql to retrieve the data from the repository (eg. Sql Server 2008, in my example). I place the result data into a POCO object. Works great :)
I\'ve formerly used L2S and am looking at using NHib along with the Sharp Architecture on a project. I\'ve started prototyping and come up against the first issue which i have no idea how to google fo
I creating a small desktop application using Qt and Poco on Mac OS X Snow Leopard. Qt works fine, but once I started linking with Poco I get the following warning: