Activities of "bmulinari"

Hi, @EngincanV thanks for the response.

I tested the change with the steps you mentioned and it did work, that is, the table created in the previous module is no longer created again in the migration for the new module.

However, I noticed that this only worked when I ran the command to remove the latest migration twice (as you instructed), and as expected that removes the last two migrations, even though the second to last migration it removes has no relation to the latest one or its tables. I don't understand why that is the case, could you please provide an explanation?

Thanks in advance.

Support, please support.

Hi, since the question was asked by @bmulinari and you have added the last response, questions become invisible from our dashboard. This is the reason why we could not prioritize to answer this question. Sorry for the late response.

@bmulinari can you please send the project again, because when I try to download the application, it gives a 502 bad gateway error? I have reviewed it before but I could not find it in my workspace for now.

I will prioritize it and will fix your problem when you send your email. So, please let me know.

Regards.

@EngincanV, I have sent the e-mail again with the code.

Hi! I apologize for the broken link. I've shared a new by mail.

Let me know if you need anything.

Hi, @EngincanV. As requested, I've sent the application code and added a bit of context to the issue mentioned here.

Let me know if you need anything else, thanks!

• ABP Framework version: v9.0.0
• UI Type: Blazor Server
• Database System: EF Core (SQL Server)
• Steps to reproduce the issue:

Hi! We are having an issue with Entity Framework migrations in our solution which consists of an application and multiple custom modules. Each module has its own DbContext, like in the approach shown here. It's worth pointing out that we are using a separate database for the tenant.

To put it simply, here's the issue we are facing:

• Module A creates Table_A
• Migration correctly adds Table_A
• Module B creates Table_B, which has a relationship to Table_A (one-to-many)
• Migration incorrectly tries to add Table_A again, in addition to Table_B

This obviously results in the error "Table_A already exists" when running the migrator. I'm not sure what we are doing wrong, but we tried a bunch of different things and the migration for Table_B is always wrong (it shouldn't try to recreate Table_A).

Any help is appreciated. Thanks!

Hi there. I see that 8.3.3 is out, but I couldn't find a mention of this in the release notes. Could you please confirm whether this issue was fixed in this release?

• ABP Framework version: v8.3.2
• UI Type: Blazor Server
• Database System: EF Core (SQL Server)

Hi there! I'm new to ABP and I wanted to ask for advice on what would be the best approach for consuming our API back-end in a Windows Forms app. This app will run on multiple clients but all will be accessing the same API endpoint in our multi-tenant solution.

As far as I could gather, my options are:

• Dynamic C# API Client Proxies
• Static C# API Client Proxies
• HttpClient with IIdentityModelAuthenticationService for authentication
• HttpClient with IdentityModel for OIDC discovery and authentication

Which one do you suggest that would fit my scenario the best? Due to my multi-tenant solution, in all of the approaches above I would need to manually specify the current tenant, is that correct?

Thank you. Just a feedback: while your workaround prevents the exception from throwing, the layout is sometimes broken as shown below:

Thank you. Are there any workarounds we could use for fixing this issue until we wait for the next release?

I sent you an email.

Thanks!