So is A0 somehow removing the implicit configuration for IConfiguration? What is the reasoning behind this?
v10.2.0 Angular .net5 abp v 6.2.0
I had a longer version of this typed up but my session was lost and along with it my original post, so here's the boiled down version.
A complete version of IConfiguration is not available to my class libraries without adding services.AddSingleton<IConfiguration>(configuration); to Startup.ConfigurServices. Without that line IConfiguration only has a single provider for environment variables. When I add the line I get a fully populated instance of IConfiguration. Prior to aspnetcore2 explicitly configuring IConfiguration for the container with aforementioned line was required, without it the injected instance would be null (such is my understanding, I never used netcore1.x versions). Starting with aspnetcore2 IConfiguration should be implicitly configured and services.AddSingleton<IConfiguration>(configuration); should not be necessary, but in A0 it seems to be.
I can find no documentation for A0 nor ABP that details this. Is this by design or a bug? If the former, can you elaborate on the reasoning and intention?
Here's what the IConfiguration instance looks like without explicitly adding it to the container:
Here's what it looks like with the explicit configuration:
A0 v10.2.0 Angular .NET 5 current ABP version 6.2.0 desired ABP version 6.3.1
Please see the following ABP issue on github: https://github.com/aspnetboilerplate/aspnetboilerplate/issues/6327
I was advised to upgrade from ABP packages version 6.2.0 to 6.3.1 to fix the issue at hand, however this has broken our app pretty thoroughly. Since A0 upgrades tend to be a brutal process, we're avoiding upgrading until v11 is out and stable, and .NET 6 is supported. Is there a way we can do this minor version upgrade of ABP in the meantime?
So how does it work? same entities created through a project with History disabled will not store history, but if those entities are added/modified via another project it will store. Or Entites defined in a project with History disabled will not store and History anywhere in the solution?
Does AspNet Zero uses any particular graphql package in angular, or do you have any recommendation?
can you let me know the best practises around enabling/disabling EntityHistory Apparently you can toggle this on every project. Does any take precedence over the other?
Configuration.EntityHistory.IsEnabled = false;
Can we directly upgrade abp version without updating AspnetZero? we are currently on 8.1
We have not, but this was supposed to be supported in 5.1 too, and not really sure if anything has changed for EntityHistory between those versions.
Re-opening this, we are still having issues with TPH entity with an OwnedType
It does work when I add mappings in the CustomDtoMapper.cs in GraphQL. I was just curious if we could enable GraphQL without using AutoMapper at all. It sounds like that it not an option, unfortunately. Let me know if I'm mistaken.
