[Suggestion] Abp.GraphDiff package

Hello @hikalkan , What do you think about creating Abp.GraphDiff package, which would allow to attach a detached entities/graphs to a context? I’m currently using GraphDiff in combination with OData and it works like a charm because updating of navigation properties are handled by GraphDiff. Let me know if you are open to such contribution and If you want I will spend some spare time to prepare an integration package, which includes the things, which are needed to make GraphDiff work out-of-the-box:

1. Some entity mapping storage for saving all of the mappings with a convenient API.
2. Custom pre-build repository which Adds/Updates entities as a whole graphs via GraphDiff.

[4nonym0us]

@maharatha , You can check out sample application, which is used in unit tests, to find out how it works.

Here is the little guide:

1. Install a corresponding Nuget-package into YourCompany.EntityFramework project and add a dependency on this package into EntityFrameworkModule.cs using DependsOn annotation. Example.
2. Add the module and configure the entity mappings for the GraphDiff. Example.
   2*. You should use the extension MappingExpressionBuilder.For<TEntity>(configuration => ...) to create new mappings.
   2**. You can find more about mappings syntax here. You use AssociatedCollection() or AssociatedEntity() to map a navigation property, but if you want to make a “deeper” mapping you firstly use the OwnedCollection() or OwnedEntity() methods.
3. Now you are ready AttachGraph() extension. This method uses the mapping configuration, which was set up in step 2. In a case, you didn’t provide any mapping, it will simply use null mapping, which means that mapping weren’t provided (it’s default GraphDiff value for mapping). Example1, Example2.

That’s it: only 3 steps to handle the detached graph attachment in EF6 using Abp. Let me know if you have any further questions or you still need a sample project.

[4nonym0us]

AbpZeroEntityFrameworkModule is module for EF6 and it’s correct to depend on it if you are using EF6. AbpEntityFrameworkCoreModule is module for EF Core. GraphDiff integration depends on EF6 and it’s the only EntityFramework module you can reference. You neither can nor should try to use GraphDiff with EF Core hence it’s functionality is already present in EF Core out of the box.

I added a Reference in my Application project to the EntityFramework project, but that made no difference so I removed it.

You must have it to resolve GraphDiff extension methods; otherwise, you will have that exact issue you’ve described in your previous message. Add the reference to EntityFramework from your Application Project, build solution, enjoy using GraphDiff.

I noticed in your example configs that you had GraphDiff installed in the same module you have AutoMapper installed in. My AutoMapper is installed in the Application module. GraphDiff is installed in the EntityFramework module.

AutoMapper is not related to the issue for sure and your module dependencies are correct.