Activities of "chrisalves"

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: 6.0.0-rc.1 (Prerelease)
• UI type: Blazor Server
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace:
• Steps to reproduce the issue:

I updated the ABP and ABP suite to 6.0.0-rc.1 (Prerelease) today and tried to create a sample application to discover the new features announced on 6.0.0-rc.1 (Prerelease).

I just launched ABP Suite, and selected the following fields to create the application and figured out that the applicantion does not run in my local computer. I believe that something is missing in the SUITE when creating the solution. The stable version (5.3.3) works very well, but the prerelease is failing)

Here below is the outputs from ABP suite command line screen.

Here is the Wizard asking for initial build and seed

After this, I´ve tried to run the application using Visual Studio, but after the browser launches the application, nothing is shown in the browser, many alerts appears in the Visual Studio outputs, and many error messages appear in the Server side.

Here is the initial step to build and run the sample application

Multiples warnings on Visual Studio presented below:

The building output has warnings:

<br>

Additionally, the appsettings.json does not contain the Authentication Server or remote server:

There are many errors in the Console of DEV Tools of Chrome:

Please, help.

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v5.3.1
• UI type: Blazor WebAssembly PWA
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): No / no
• Exception message and stack trace:
• Steps to reproduce the issue:

1. Create a New Solution using ABP Suite as the picture below. The feature "Public Web Site" is not selected. This is causing the application do not run.
2. ABP Suite creates the new application
3. Seed the Initial Data
4. ABP executing the Initial Seed in the created database and builds the application
5. The application is created with success according to the Popup
6. Create a simple Entity like "Customer" and add a simple property like "Name" with 50 of max size and required as pictures below: (Entity)

(Property)

7. Hit the buton "Save and generate".

8. Select the buton "Yes"
9. The application is being built
10. You will see an error at the end of this process.
11. The Database was created with success
12. Try to build and RUN the HttpApi.Host manually using Visual Studio 2022 (same used for other projects), selecting this project and using CRTL+F5
13. See the error presented by Visual Studio during the Build process.
14. Read the Error description after this process

Severity Code Description Project File Line Suppression State Error CS1061 'IServiceCollection' does not contain a definition for 'ForwardIdentityAuthenticationForBearer' and no accessible extension method 'ForwardIdentityAuthenticationForBearer' accepting a first argument of type 'IServiceCollection' could be found (are you missing a using directive or an assembly reference?) MyApp.HttpApi.Host D:\Data\visualstudio\MyApp\src\MyApp.HttpApi.Host\MyAppHttpApiHostModule.cs 157 Active

I´ve tried to create this app many times, without success. ABP Suite only works fine if the feature "Public Web Site" is selected in the begining of the process. I have other applications created with sucess if the feature "Public Web Site" is selectec. I´m trying to create a new application withou "Public Web Site" because I do want to avoid to install Redis Cache, required by the Public Web Site.

I believe this is an error injected recently in the ABP Suite.

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v5.3.0
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace: Blazor Server receiving error message 500 when trying to access the Aplication API
• Steps to reproduce the issue:" To create an application using ABP Suite, select "Application Template", UI Framework "Blazor WebAssembly", Mobile "React Native", Database "Entity Framework Core", Database SQL, check "Public Website", check "Cms-Kit", check "Separeted Tenant Schema" and check "Progressive Web Application". Build the solution and run locally in the PC to to ensure it runs locally perfectly. Prepare the projects to be published using Visual Studio to remote servers (I´m using Azure WebApp) setting them up by the appsettings.json file in Blazor Projetct, DB Migration and HostAPI project changing the URL of the new web servers. Define the remote servers with configuration settings for ASPNETCORE_ENVIRONMENT=Staging to define the environment name, the same used by the projects".

I will present the settings prepared to publish the application. No sensitive information.

appsettings.json file for Blazor project is presented below containing the new Blazor and HttpApi.Host endpoints.

appsettings.json file for HttpApi.Host project is presented below containing the CorsOrigins and RedirectAllowedUrls containg the Blazor endpoint.

appsettings.json file for DbMigrator project is presented below, with the endpoints for Blazor and the API defined for the remote servers.

After the publish is done, the Swagger runs fine, so the API endpoint seems to be well configured as presented below:

But the Blazor front end is loading endless as presented below:

I´ve already rebuilt the application to avoid mistakes. I searched on the web, also on the ABP support and community and reviewed the settings. I found many other folks having the same issue reported in the support and comunity. I believe there is a trick that is missed by blog authors on community also in the answers from support tickets found.

Here is the symptons found using the "Dev tools" available in the Google Chrome browser:

here is an additional information on the "network" available in the "Dev tools" presenting many failures:

Here is the check-point about the endpoint being pointed correctly by the Blazor app:

Here are the detailed screens that might be the problem: Screen 1:

Screen 2:

Screen 3:

Screen 4:

I´m really blocked for a long time trying to find a solution by myself but I was not able to find what is going wrong with the settings.

Please help on this! 😊

Best Regards,

Christian

<br> <br> <br>

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v5.2.2
• UI type: Blazor
• ABP Suite: Yes
• ABP Suite Version: v5.2.2
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Soution has Public Web Site project: Yes
• Exception message and stack trace:
• Steps to reproduce the issue:"

I created Solution containg a Blazor App, Web API ({appname}.HttpApi.Host) and Public Website using ABP Suite as shown by the picture below:

At this moment the solution was created with no additional entities. The solution containing multiples projects (Blazor App, Wep API, Public WebSite) was synchronized with Github repository, additionally it was created 3 branches named "Development", "Staging" and "Main" to allow 3 distinct environments for the software lifecycle.

We created the Microsoft Azure WebApps integrated with Github using the standard Azure wizard during the WebApp creation process (using the wizard), and just set manually the project path to the CSPROJ file in the YAML for each project. We created a "Azure Cache for Redis" service in Microsoft Azure to support the "Public Website" considering the documentation requirements to have Redis available for caching the Public Website. We created 3 distinct database instances using Azure SQL Server to support each of 3 environments.

The WebAPI is published on each AzureWebApp pointing to the right database instance.

How can we propagate the Database Migrations when we create or change any Entity using ABP Suite? In the Local Database at my PC where I´m running ABP Suite, the changes were applied automatically by ABP Suite. Once I sync with the remote repository and commit using Github to "Development" branch, the Github automation starts a new deployment to Azure WebApp instance but I could not find a way to apply the changes to remote database instance automatically, the only way I could do this migration was by running manually the project DbMigrator existing in my PC (using DOTNET RUN inside the DbMigrator folder) pointing to the remote Database Instance, applying the changes manually. How can I apply the migration/changes to the Database when the new release of the WebAPI is deployed and is required to update the database instance? Is there any solution embebed WebAPI project to verify the database instance and apply the migrations?

Best regards,

Christian

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v5.2.1
• UI type: Blazor WebAssembly
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace: None
• Steps to reproduce the issue:"

Hi Folks,

I developed a simple application using Blazor WebAssembly to be hosted in Microsoft Azure, througth the Static Web App technology. The application name is eOrdering, the ideia is to be an application to allow small bakeries and restaurants to offer Online Ordering to their customers for takeawey or delivery of products.

The projects inside the Solution are named using ABP convention like eOrdering.Blazor, eOrdering.HttpApi.Host etc.

To create the Azure Machine is quite simple cause Azure offers a Wizard to set the machine and the Github settings to get access repository/branch to implement the CI-CD automation.

The machine has a public and fixed host name like https://somename.azure.com but it can be changed in the future for a custom domain name.

The beauty of this ci-cd is to allow to update the app version inside the machine when there is a new version published in Github. Everytime I commit the branch, the Github updates the Azure Machine content. It is very common nowadays but I´m describing here to make the case clear.

I have 3 branches in the GitHub (Development, Test, Production) and each of them is integrated with a distinct Azure Machine. Once there is an update in the Development branch, the new code is automatically deployed to Azure Machine-dev and need to access the correct API. When there is a change in the Test branch, the new code is automatically deployed to Azure Machine-tst, and the same situation occurs when updating the Production branch.

In my personal PC where I have ABP installed and Visual Studio to run, I can see the both applications running correctly (the API and the FrontEnd) but when I publish them to Azure, the FrontEnd doesn't find the API.

What kind of configuration should I need to add to Blazor frontend application (or another dependency project) to allow the application understands that is being hosted by a given machine and use the correct path to start the communication with the correct backend API (in the case the project eOrdering.HttpApi.Host) hosted in another manhine)?

Many thanks!

• ABP Framework version: v5.2.0
• ABP Suite: Yes, v5.2.0
• Template Type: Application Template
• UI type: Blazor WebAssembly
• DB provider: EF Core
• Database: SQL Server
• Tiered (MVC) or Identity Server Separated (Angular): There is no separated Identy Server.
• Exception message and stack trace: Blazor App error when run using Visual Studio (CTRL+F5)
• Steps to reproduce the issue:" I created a simple application to try the feature Many-to-Many, with a single field (name) considering 2 entitys (product and catalog). The application worked fine, I was able to run the HttpApi.Host and Blazor. After that, I decided to create additional fields on ABP Suite in the Entity Products. After that, I selected to "Save and Generate". This process took a long time and at the end I saw an error message related to the Migration. I repeated few times the execution of "Save and Generate" but now it runs without problem but something was not done in the solution because the Blazor is not running anymore.

If I select to run the Last Sucessful build, it runs but it does not present the new fields created. I do not know how to solve the issues related to this Bulld errors.

Hi,

I was working today with ABP Suite and also with Visual Studio for Windows, building a new solution. I realized that the ABP suite stopped work and I closed the command prompt and tried to run/load it again. I realized the Suite was not being launched in the browser, so I rebooted the pc few times, also removed the ABP suite, rebooting again. Reinstalled and the same problem persists. I cleaned browser cache and history, but it is still the same, not being loaded.

Any thoughts about it?

Bellow you will see the answers required, also two screen shots for the command prompt and the browser. Thanks for your support.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v5.1.3
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace:
• Steps to reproduce the issue:"
•