Dear Support,
We just updated from 7.04 to 8.2. I made the changes that were noted in the migration guide:
https://docs.abp.io/en/abp/latest/Migration-Guides/Abp-8_0 https://docs.abp.io/en/abp/latest/Migration-Guides/OpenIddict4-to-5 I also created a database migration and updated the database. And i ran "abp install-libs" to be sure.
The admin interface is up and running and our application works as excpected. So far so good!
The only issue we have is:
When navigating to: /openIddict/Applications i get the following error (and the "Application Type" collumn is not filled):
I guess this has to do with the openiddict change? Any idea how i can fix this?
Reproduction Steps No response
Expected behavior The error should not be visible and the column "Application Type" should be filled correctly.
Actual behavior No response
Regression? No response
Known Workarounds No response
Version 8.0.2
User Interface MVC
Database Provider EF Core (Default)
Tiered or separate authentication server None (Default)
Operation System Windows (Default)
Other information No response
Kind Regards,
Alfred
ABP version: 4.2.1
Steps to reproduce:
I then added the "CustomerX.ApiY" projects necessary to the solution. Because the API has no dependency on a database (it is used to call a thirdparty api) I removed everything which is related to databases (removed the nuget packages, and all the code related).
So this gives me this solution:
And this is the HostModule for the (httpApi.Host) module:
I then run the Suite to add an entity but it gives me this error when i click : Save and Generate:
"Error occurred on DB migration step: MSBUILD : error MSB1009: Project file does not exist. Switch: ../CustomerX.HttpApi.Host Unable to retrieve project metadata. Ensure it's an SDK-style project. If you're using a custom BaseIntermediateOutputPath or MSBuildProjectExtensionsPath values, Use the --msbuildprojectextensionspath option."
I think it is still trying the run the migrations for the CustomerX.ApiY module? All entity files are created correctly but the only thing that is failing, is creating the DB migrations.
Is there a way to fix this?
Kind Regards,
Alfred