Any documentation for CI/CD deoploment on Azure DevOps. I want to deploy my Asp.net zero Core / Angular project on Azure Devops
What is the best practice for the case when we want to make a direct database call, like a stored procedure. Typically with Entity you can get at this from the db context but the db context is extracted a bit away from us with AspNetZero. We would want to utilize the frameworks connection management and transaction management if possible rather than just instantiating a sql connection outside the framework.
Any suggestions?
Thanks
Thanks! that was exactly what I was looking for.
Azure has recently updated all their build agents to Core 3.1. We are using the the Core version 2.2. All of a sudden we are seeing users being kicked out of the system throughout the day and in the logs we see
System.Exception: There is no user: 28
I believe in the multi-tenant structure it should have a tenant appended to that like 28@2 or something. I know core 3.1 changed how multi-tenancy works but am not sure how exactly its implemented in the framework here.
We tried changing the build agent to force using the 2.2 SDK and are waiting to see if this has a result but I wanted to open a ticket to see if anyone else is having this issue or has any ideas.
Thanks in advance.
Single database and user Belongs to a tenant. This worked perfect until this week when we deployed on Sunday but there are no code changes related to tenacy and we have not updated the framework.
The only change is the build agents are now running the latest 3.1 and core is weird in that if you do not specify the SDK version it will try to build with the latest SDK.
There are breaking changes to the way multi-tenancy works in 3.1 but I havne't been able to dig into the base code to figure out how it uses multi-tenancy in the middlware. https://michael-mckenna.com/multi-tenancy-compatibility-dot-net-core-three
I've forced the azure pipeline to use the 2.2 SDK and rebuilt the same exact code and so far the issue seems resolved, but this isn't ideal long term.
We are confident now that the downgrade of the SDK on the build agent resolved the issue. What is the path forward with this?
We are also running v7.0.
Thats fair but for right now any idea why in production we are seeing our users get kicked out throughout the day and seeing errors in the logs related where the Get user is called with a user ID and no tenant? The 2.2 version still was a production release that we paid for. We will try to upgrade soon but we need to get people not kicked out.
So the issue is not resolved. It is still lingering and people are getting kicked out somewhat regularly. We see an error in the logs that looks like this:
These are multi-tenant users so that looks very wrong. It should look like this:
I've inspected the bearer tokens and they have the tenant in them. All the multi-tenant functionality seems to be working well besides this sporadic logout.