CleanArchitecture | repository contains the implementation | Architecture library

I am having trouble wiring up identity into Blazor server with ASP.NET Core identity. Specifically getting the correct logged in state in Blazor pages (while I am getting them from the Blazor pages).

I think it's related to some of the startup being initialized in another project - but not sure how to debug it or what the solution is to be able to get the logged in state correctly.

Reproduction steps and link to GH repo below as a POC.

Background

I'm porting over the clean-code project by JasonTaylor from Angular / ASP.NET Core to a Blazor server project with ASP.NET Core Identity.

Issue

The application runs up and I can browse the pages when I register I can see logged-in state in the identity-based default pages but in the Blazor pages that use the AuthorizeView (e.g. LoginDisplay.razor) it's not aware of being authorized.

Startup in the Blazor project:

What is the best way to call a SQL function / stored procedure when converting code to use the repository pattern? Specifically, I am interested in read/query capabilities.

Options

1. Add an ExecuteSqlQuery to IRepository
2. Add a new repository interface specific to the context (i.e. ILocationRepository) and add resource specific methods
3. Add a special "repository" for all the random stored procedures until they are all converted
4. Don't. Just convert the stored procedures to code and place the logic in the service layer

Option #4 does seem to be the best long term solution, but it's also going to take a lot more time and I was hoping to push this until a future phase.

Which option (above or otherwise) would be "best"?

NOTE: my architecture is based on ardalis/CleanArchitecture using ardalis/Specification, though I'm open to all suggestions.

I'm getting this error:

Database operation expected to affect 1 row(s) but actually affected 0 row(s)

when adding a new element to the entity's collection.

Base classes in Domain project:

I was trying to publish a solution using Visual Studio but I'm really stucked at this point. I got my little project using Clean arhitecture solution template but when trying to publish it nothing seems to work.

What I've tried:

• publishing each project one by one, but the frontend (angular) won't communicate with the backend(.net core)
• updating node and python
• reinstalling python and node
• running the visual studio by administrator
• trying to publish the template from github, without my very own code in it
• update the csproj file from npm run build -- --prod to npm run build --prod

I also tried to look for this error on the internet, I already tried every solution but nothing seems to work for me.

You can find here a picture of the console: Link to the image

I'm using Jason Taylor's Clean Architecture template and I wonder why his WebUI Dockerfile is generated by Visual Studio just like below.

It sets WORKDIR to /src and then copies each project from /src/ProjectDir/Project.csproj. What's the point of WORKDIR in that case? Look at WORKDIR "/src/src/WebUI". Why /src/src? There is only one src directory.

I want to add items to test database for integration test . These tables have many-to-many relation (I config them in database context) I want to add new record to watchlist table but AddAsync throws DbUpdate Exception

Violation of PRIMARY KEY constraint 'PK_Movies'. Cannot insert duplicate key in object 'dbo.Movies'. The duplicate key value is (f48bd131-79ad-47bc-8cf2-1ece8ba648c2). The statement has been terminated.

EF thinks I want to update movie entity but I want to add item to Watchlist and link table (MovieWatchlist)

my project is base on CleanArchitecture

I have a .net Core 3.1 app running in an azure web app for containers(linux) service. This app is a web api project with an angular 9 front end. It uses Identity server 4 for authorization.

For reference I am using this clean architecture framework template for my project (the add docker support pr).

The app runs in the service just fine. The front end works and I can "log in" using ID4 and I can see that the authorization token are returned when I log in.

When I make a call to the backend web api from the front end angular client app I get the following error:

I am trying to use the .Net Core Clean Architecture App Template and get it running in containers and deployed through an azure CI/CD pipeline

I have the containerized version of the template running locally in linux container with port 5001 and everything works perfectly.

I have the azure pipeline build process working properly and it creats image in my container registry.

The problem is once I deploy/release to a Web App for Containers, the app fails and throws the following error:

Application startup exception System.InvalidOperationException: Couldn't find a valid certificate with subject 'CN=localhost' on the 'CurrentUser\My' at Microsoft.AspNetCore.ApiAuthorization.IdentityServer.SigningKeysLoader.LoadFromStoreCert(String subject, String storeName, StoreLocation storeLocation, DateTimeOffset currentTime)

What I have done:

1. Following these docs from MS I have created a local dev cert:

   dotnet dev-certs https -ep %USERPROFILE%\.aspnet\https\aspnetapp.pfx -p { password here }

   dotnet dev-certs https --trust

2. I then imported this into the Web App as a private .pfx cert.

3. I added an application setting WEBSITE_LOAD_CERTIFICATES with the "thumb" value of the cert

4. I used the "hostname" of the imported cert in the Identity Server appSettings.json section (hostname=localhost in my case)

When the Web app loads, it shows :( Application error and the docker logs give me the error I quoted above.

I am pretty sure this is related to the Identity server set up and the appSettings.json values here:

I have a .net core 3 app running locally/development just fine, both on its own and when run in a linux container. I then take the app and have it built into a docker image inside azure pipelines. The image is loaded to azure container registry.

Finally, I have an Azure Web APP for Containers (Linux) that uses the image to run.

Locally I have the docker-compose file set up like this: