How do I write my BLL to make it re-usable?
Most of it was written 4-5 years ago. Our teams long term objectives are to use Entity Framework. Though we aren’t gonna do it right away as our deadlines aren’t allowing us to do so.
Now we have our own framework. I want to be able to segregate the Business logic layer in such a way that it need not be re-written when we move to EF. Please guide us with best practices, advise us in this direction.
How do I write my BLL to make it re-usable?
Most of it was written 4-5 years ago. Our teams long term objectives are to use Entity Framework. Though we aren’t gonna do it right away as our deadlines aren’t allowing us to do so.
Now we have our own framework. I want to be able to segregate the Business logic layer in such a way that it need not be re-written when we move to EF. Please guide us with best practices, advise us in this direction.
Should an ASP.NET MVC application directly use Entity Framework as the model?
I’m building my first MVC application in Visual Studio 2013 (MVC 5) and I’m a bit unclear on the best way to setup my model.
Should an ASP.NET MVC application directly use Entity Framework as the model?
I’m building my first MVC application in Visual Studio 2013 (MVC 5) and I’m a bit unclear on the best way to setup my model.
Should you reuse an Entity Framework EDMX between multiple solutions?
We currently have 1 giant EDMX for our corporate database. It, along with all of the generated POCOs, are in a separate project (we’ll call it the EDMX project) which we pull in to any solution that uses the main database. In other words, any new application we develop uses this same EDMX project. Naturally, the EDMX project requires a reference to Entity Framework. But so do the main projects for each application. Thus, a given solution has 2 separate Entity Framework references – which could end up being completely different versions.
Should you reuse an Entity Framework EDMX between multiple solutions?
We currently have 1 giant EDMX for our corporate database. It, along with all of the generated POCOs, are in a separate project (we’ll call it the EDMX project) which we pull in to any solution that uses the main database. In other words, any new application we develop uses this same EDMX project. Naturally, the EDMX project requires a reference to Entity Framework. But so do the main projects for each application. Thus, a given solution has 2 separate Entity Framework references – which could end up being completely different versions.
Should you reuse an Entity Framework EDMX between multiple solutions?
We currently have 1 giant EDMX for our corporate database. It, along with all of the generated POCOs, are in a separate project (we’ll call it the EDMX project) which we pull in to any solution that uses the main database. In other words, any new application we develop uses this same EDMX project. Naturally, the EDMX project requires a reference to Entity Framework. But so do the main projects for each application. Thus, a given solution has 2 separate Entity Framework references – which could end up being completely different versions.
Should you reuse an Entity Framework EDMX between multiple solutions?
We currently have 1 giant EDMX for our corporate database. It, along with all of the generated POCOs, are in a separate project (we’ll call it the EDMX project) which we pull in to any solution that uses the main database. In other words, any new application we develop uses this same EDMX project. Naturally, the EDMX project requires a reference to Entity Framework. But so do the main projects for each application. Thus, a given solution has 2 separate Entity Framework references – which could end up being completely different versions.
How to store a potentially large amount of optional properties of objects?
I’m using Entity Framework Code First with ASP.NET MVC. This handles my database design based on the domain models within my application.
How to store a potentially large amount of optional properties of objects?
I’m using Entity Framework Code First with ASP.NET MVC. This handles my database design based on the domain models within my application.