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
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.
Thanks! that was exactly what I was looking for.
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
Any documentation for CI/CD deoploment on Azure DevOps. I want to deploy my Asp.net zero Core / Angular project on Azure Devops