@galip fyi
hi murat,
I can say, this is not included in the milestone plans in the upcoming 6 months. If you want to implement this on your side I can share you a link https://dottutorials.net/dynamic-user-defined-dashboards-asp-net-core-tutorial/
thank you Sturla
Multiple Active Result Sets (MARS) is a feature that works with SQL Server to allow the execution of multiple batches on a single connection. When MARS is enabled for use with SQL Server, each command object used adds a session to the connection. You can enable it by adding MultipleActiveResultSets=true to the connection string.
If two batches are submitted under a MARS connection, one of them containing a SELECT statement, the other containing a Data Manipulation Statement, the Data Manipulation Statement can begin execution within execution of the SELECT statement. However, the Data Manipulation Statement must run to completion before the SELECT statement can make progress. If both statements are running under the same transaction, any changes made by a Data Manipulation Statement after the SELECT statement has started execution are not visible to the read operation.
This says that if you enable MARS your queries will run in parallel and will result in ambitious results if you run in a transaction. MARS operations are not thread-safe.
There's a very good Microsoft doc on why you need this: https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/sql/enabling-multiple-active-result-sets#special-considerations-when-using-mars
In general, don't add MARS if you don't know what it does.
@christophe, can you pls create a new topic for the new question. when we solve the major issue we generally close the ticket. this is good for others to track the issue.
Manually adding the "~" symbol to Url
this is right! We have also done that in the new versions.
if you are using Virtual Directory local URLs must start with ~ , otherwise just / is enough
And I tried the production environment, the problem disappeared
do you have still this issue at the moment?
this sounds like you need to mock the IWebHostEnvironment in your test module.
I'll show you how to do that;
https://support.abp.io/QA/Questions/1077/Testing-Overridden-AppService#answer-1bbd38f2-5f8c-36ad-6eeb-39fb70a23930
@mehmet what do you think?
check your database table: IdentityServerClientRedirectUris
if you are using the default URLs, those are configured for local development.
Replace all your localhost URLs to your production addresses.
