أنشطة "LW"

Is this a new limitation? This worked fine earlier.

Ok. that " context.Services.AddAlwaysDisableUnitOfWorkTransaction();" actually brought another problem for us. With some of our integration tests, we use test collection to speed up the test execution. We used the transactional unit of work to control the system state, so the tests were not dependent on each other. System state changes were rollbacked after the test. Now that the transactions are disabled, these tests are now interdepended and some query tests fail because another test has affected the database state. I know that Abp recommends to do the test initilization per test, but with larger test sets, that makes the test excecution slower and slower. Is there any way to control the transaction separately per test now? Is there any other good way to speed up the test excecution with larger amount of integration tests?

hi, that seemed to fix the problem.Awesome, Thank you! Can you please explain why that helps, so I can put a comment in our code?

Same here :(

I found out that we have this kind of configuration var redis = ConnectionMultiplexer.Connect(configuration["Redis:Configuration"]); var dataProtectionBuilder = context.Services.AddDataProtection().SetApplicationName("ABC"); dataProtectionBuilder.PersistKeysToStackExchangeRedis(redis, "ABC-Protection-Keys");

I can see two different options to discriminate the data between the deployment stages: either define the stage in application name or Redis key name ( ABC-Protection-Keys). The question is which should we use and should we set different application names for the identity server and the web application?

Ahh, I missed that it was related to tawk to integration which we have used in our application. Thank you for your answer!

• ABP Framework version: 5.1.2
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes

Any ideas for this?

ABP Framework version: v5.1.1

UI type: Angular

DB provider: EF Core

Tiered (MVC) or Identity Server Separated (Angular): yes

Problem: After the update from 4.3.0, our Angular client is refreshing the token every second. I assume this is not normal. Can we adjust the refresh interval somehow or is there a bug somewhere?

Ok, thanks for your answer. I'm also interested in the longer version of the answer :) In what situations do you see it's ok not to use that method? Suite templates and at least earlier versions of easy CRM do not implement this. Is this a coming change to the templates?