Develop Reference

Adding additional properties to dll class

I have been given dlls for entities, service classes. I need to add additional properties to Entity in my web project. How can I do that? I cannot create new classes extending dll classes because service dll returns Entity class defined in the dlls.
Is there any way?
thanks
Sanjivani

Can I share entities between solutions?

I have a problem with sharing entities in 2 different solutions.
I have one entity (Country) that I need in 2 solutions. One solution it's a web application and the other it's a console application but I need this entity in both.
Additionally, we are doing migrations and I don't know what the behaviour of code first is in this case if I change the entity twice one per solution.
It is possible to share entities between solutions in entity framework 6 code first?

If I understood correctly you want to use an entitie which is contained in a project and use it botjh in a web project and a console project. You can do that by referencing the output dll of your entities project from where you need it.
In your case you would add a reference to entities.dll on the consoleapplication project and another one on the webapplication project.
Personally I would have all the projects in the same solution and reference each project I needed. But it is possible to do it your way.

How to avoid references to Entity framework in multiple projects

I want to encapsulate Entity Framework in one project. This project will do DB access alone. When updating, I want to map a domain model to EF. The purpose is that other layers of the solution should have no knowledge of infrastructure.
My problem is that I need to reference EF in my "caller" project to make it work.
Is there a way to avoid this?
Solution
- ConsoleProject
- EntityFrameworkProject (EF from Nuget)

With EF6 and code based configurations, this is now possible.
[DbConfigurationType(typeof(MyDbContextConfiguration))]
internal class MyDbContext : DbContext
{
public DbSet<MyModel> MyModels { get; set; }
}
internal class MyDbContextConfiguration : DbConfiguration
{
public MyDbContextConfiguration()
{
SetProviderServices("System.Data.SqlClient", SqlProviderServices.Instance);
}
}
If you configure your database in Project A as above, then only Project A needs to reference EntityFramework, and any project that references it, like Project B will not try to find the provider in its own assembly.
Expose your repositories in Project A, and add a <connectionStrings> configuration in Project B, and it should work flawlessly.

I used this approach: https://stackoverflow.com/a/22970805/3874212
I reference the EntityFramework.SqlServer.dll only in the Console startup project.
I install entity Framework in my other project.
I create my model from DB in EF project
I move the connection string from the app.config in EF project to the Console project.

Unfortunately it is not possible for some strange reason. You must include EF package in client application too, not only in data access library.
It is possible to include only that DLL redlaz mentioned, but by doing this you are cooking lot of potential problems with versions.
Just overcome all reluctance and add EF package to your client application too.

Entity Framework - Multiple CLR Types

I am getting the following error when executing one one of my LINQ queries
The mapping of CLR type to EDM type is ambiguous because multiple CLR
types match the EDM type 'Product'. Previously found CLR type
'TF.MyProject.DAL.Product, newly found CLR type
'TF.MyProject.DTO.Product'.
The Entity Framework generated class and the DTO object both are under their own namespace. This has worked previously and below is what I have tried so far...
Regenerated the EDMX Model
Removed and Created a new EDMX Model
Run Custom Tool to generate the Template files
Ensure all projects within the solution are using the same Entity Framework version.
Entity Framework version: 6.1.3
Below is how my current project is set up
MyProject
/DAL/MyProjectModel.edmx
/DTO/Product.cs
Any idea or suggestions will be helpful. This has worked in my previous projects with version 6. Not sure if it is specific to a version within release 6..
Note: Moving the DAL to a project of its own resolves the issue

You have two classes with the same name Product. Entity Framework uses Class Names only, irrespective of namespaces or files where it is declared. The error message clearly says you have two Product classes, one in TF.MyProject.DAL namespace and another one in TF.MyProject.DTO.
Try renaming on of these Product classes to some other name and try again.

Move generated classes after Reverse engineer code first used in Entity Framework Power tools beta 2

I am using Entity Framework 5.0 with Entity Framework Powertools beta 2. We have a database that we are not allowed to change and so are using the Reverse Engineer Code First option to create the classes. The generated classes are placed in the Models folder below the mappings.
Is there a safe/best way to move these generated classes into their own project, leaving the DbContext-type class and the Mapping file classes in the Models folder?

There is no problem with moving the entities to whatever project and/or namespace you like. Just copy the files to where you want them. You will, however, likely want to go in and change the namespaces on every file (though it's not specifically required).
You do of course have to add a reference to your new assembly to your parent project.