I have a v7 Angular project that uses IdentityServer that I'm to upgrade to 11.4.2. I also see that support for IdentityServer is being dropped in v12.
Anyway -
After getting migrations straightened out, the login for the host loads.
I can step through the code and successfully authenticate in the POST on login method of UiController.
However, when it redirects to index, and GetCurrentLoginInformationsAsync is called from the sessioncache, the credentials are lost.
AbpSession is not set, essentially.
In my logs, I see several issues related to cookies that look like this:
The cookie 'idsrv.session' has set 'SameSite=None' and must also set 'Secure'.
The cookie '.AspNetCore.Identity.Application' has set 'SameSite=None' and must also set 'Secure'.
The cookie 'Identity.External' has set 'SameSite=None' and must also set 'Secure'.
Additionally, I'm seeing this error:
Unable to configure browser refresh script injection on the response. Consider manually adding '<script src="/_framework/aspnetcore-browser-refresh.js"></script>' to the body of the page.
Do these error messages indicate an obvious misconfiguration or misstep on my part? Are there any items I should check?
Thanks in advance for any tips on resolving this issue.
It turns out there were migrations that had been applied in the versions between ours and target version (11.4).
We identified those and copied the migrations into our project and it successfully compiled and is partially working.
V7 & v11 Angular
Trying to upgrade a v7 to v11 existing project, some migrations are not in the history table.
The previous dev is not available for context in this situation - however -
The table I'm currently seeing causing a problem is AbpEntityChangeSets.
The migration is not in the history, but the table exists and has data in it.
Am I safe to comment out the everything in UP()?
I've had good results with Wijmo controls. Not cheap, but worth it for my project.
I've wrestled with how to do this for a while. This framework claims to be DDD leaning -- however it violates one of the most important DDD concepts, which is -- Repositories should be per Aggregate Root and NOT per Entity.
I've gotten to know the ABP code pretty well in this area, and it is obvious that this was designed to violate this concept and intended to have a repository per entity.
What is the best way to adhere to this critical DDD concept -- Repositories only for Aggregate Roots -- within the ABP framework?
Yes thanks, I've been using that method you suggested.
This basically reduces IRepository to an IQueryable using EF Core.
I gotta say, after a few projects trying to put a repository abstraction on top of EF, I'm not a fan of this abstraction... Could someone please explain why it is necessary in this framework?
Hello,
What is the recommended way to load related data using the IRepository pattern and EF Core?
EF Core has a way to load related navigation properties, and to continue down the chain with .ThenInclude calls.
I see EnsureLoadedAsync was added recently, but it does not accomplish these two things I need:
Any tips?