Activities of "Frontis1"

It exists as a column:

But it does not contains any values:

So now i re-saved all the applications and now they are filled AND the error is gone:

👍

So for now we have a workarround!

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

To the main project

Hi Alper,

Thanks for your quick response.

abp add-module ProductManagement --new --solution C:\YourSolutionPath --add-to-solution-file

Is not adding the pro version of the module template (https://docs.abp.io/en/abp/latest/Startup-Templates/Module). For instance, I am missing the host folder:

I just noticed that the ABP suite is not using the pro version as well when you use the "Create new module" button:

That's why I used:

abp new CustomerX.APIY -t module-pro --preview --create-solution-folder --output-folder p:\development\CustomerX\modules --no-ui

because this command WILL add the host folder! But, as far as i know, there is no way to add it to an existing solution?

But nevertheless i still feel that the ABP suite is containing a bug for solutions which have modules in them, because "save and generate" keeps failing when i create a new entity in the suite. And that is the reason we bought the license.

Just perform these simple steps and you will see:

1. run: abp new CustomerX -t app-pro --create-solution-folder --preview --output-folder p:\development\
2. run: abp new CustomerX.APIY -t module-pro --preview --create-solution-folder --output-folder p:\development\CustomerX\modules --no-ui
3. Run the DBMigrator so the database get's created and seeded.
4. Start the abp suite en open the solution in the abp suite.
5. Add a new entity and press "Save and generate"
6. Notice that an error occurs

Hi Alper,

Thanks for your response. This works indeed.

But what would be the equivalent CLI command?? We would rather add modules via the CLI so we can easily automate our solution-creation.

I also noticed that when we do the following:

1. run: abp new CustomerX -t app-pro --create-solution-folder --preview --output-folder p:\development\
2. run: abp add-module CustomerX.ApiY --new --add-to-solution-file
3. Run the DBMigrator so the database get's created and seeded.
4. Start the abp suite en open the solution in the abp suite.
5. Add a new entity and press "Save and generate"

everything works as well!

But in step 2 we use the add-module and this will not add the pro-module unfortunately. Is there a add-module cli command that will add the pro version?

Sorry, have to reopen this. I did some testing this morning and the error did not occur so i thought it was a fault on my side but i just got the error again and pinpointed the issue.

To reproduce:

1. run: abp new CustomerX -t app-pro --create-solution-folder --preview --output-folder p:\development\
2. run: abp new CustomerX.APIY -t module-pro --preview --create-solution-folder --output-folder p:\development\CustomerX\modules --no-ui
3. Run the DBMigrator so the database get's created and seeded.
4. Start the abp suite en open the solution in the abp suite.
5. Add a new entity and press "Save and generate"

Notice that an error occurs:

"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."

To fix this you can do the following:

Open the abp suite and open the solution BEFORE adding the module OR move the "modules" folder temporary and open the solution in the abp suite.

My guess is that the msbuildprojectextensionspath is not getting set correclty when the module is already in the solution folder.

When the error occurs i noticed that the suite has made a OBJ directory in the wrong path:

So there is definitely somthing going wrong with a path.

Cant reproduce this issue anymore myself. Case closed!

ABP version: 4.2.1

Steps to reproduce:

• abp new CustomerX -t app-pro --create-solution-folder --preview --output-folder p:\development\
• abp new CustomerX.APIY -t module-pro --preview --create-solution-folder --output-folder p:\development\CustomerX modules --no-ui

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