Mapping a legacy database to ORM using wrapper classes
I want to use an ORM with a legacy database, but I don’t want to expose some of the underlying data types. For example, some of the columns are nullable doubles or floats and I want my domain model to use non nullable decimals.
Is there a better way to model a many-to-many relationship on the same table with Entity Framework?
The context We’re building a web application using Entity Framework 5.0. One of the requirements is that it should be possible for the administrators to link related products so that when someone browses to a product we can render a list “You might also like these products:“. Since a product can be linked to many […]
Why should I use List over IEnumerable?
In my ASP.net MVC4 web application I use IEnumerables, trying to follow the mantra to program to the interface, not the implementation.
Why should I use List over IEnumerable?
In my ASP.net MVC4 web application I use IEnumerables, trying to follow the mantra to program to the interface, not the implementation.
How do I split out a service layer
I currently have four projects in my website’s solution:
Is Entity Framework only for Asp .NET / Asp. NET MVC? [closed]
Closed 11 years ago.
What is the rule on passing around collections? List vs. Ienumerable vs. IQueryable
I do Entity Framework stuff using repository patterns that are passed to the controller to than be called by the client using jquery AJAX.. Is there any basic rules on in what format I should be passing around these lists? Within the server code I suppose I could just pass around an Iqueryable? yes? And to the client I could pass around a list version ? That is my first guess..
what’s a good approach to working with multiple databases?
I’m working on a project that has its own database call it InternalDb, but also it queries two other databases, call them ExternalDb1 and ExternalDb2. Both ExternalDb1 and ExternalDb2 are actually required by a few other projects. I’m wondering what the best approach for dealing with this is?
what’s a good approach to working with multiple databases?
I’m working on a project that has its own database call it InternalDb, but also it queries two other databases, call them ExternalDb1 and ExternalDb2. Both ExternalDb1 and ExternalDb2 are actually required by a few other projects. I’m wondering what the best approach for dealing with this is?
ado.net or EF for a point-of-sale system
We have a point-of-sale system that was developed using ado.net, our current concern is to make the application real fast in creating transactions (sales). Usually there are no performance concerns with high end PCs but with with low end PCs, the transactions take really slow.