Starts in:
2 DAYS
2 HRS
3 MIN
35 SEC
Starts in:
2 D
2 H
3 M
35 S

Activities of "ezarmer"

I have to admit that I'm very disappointed with ABP for several reasons. However, that's a topic for another post. Currently with using the 8.1.4 release and selecting a Blazor Server application there seems to be several bugs. First, the templating format is horrible. The code is all over the place in the .razor pages. Secondly, I created multiple enums in the ProjectName.Domain.Shared directory per documentation. I make use of ABP Suite to create my new entities and select all the options. During the creation of the entity it errors out. The reason for this seems to be two-fold. The first reason is due to the fact that the application code is looking for a namespace ProjectName.Shared (which obviously doesn't exist). The second is due to incorrect code either on the front-end or backend, depending on what ABP has intended. For instance, the following code is what is present during the creation of a new entity with delete and excel export selected:

This is the code in the .razor page. GetMedicationCollectionLookupAsync

This is the code in the code behind file (generated and unaltered). GetMedicationLookupAsync

Please address this as soon as possible. I need to get this application out as soon as possible.

  • ABP Framework version: v8.1.x/8.2.x
  • UI Type: Blazor WASM / Blazor Server
  • Database System: EF Core (SQL Server)
  • Tiered (for MVC) or Auth Server Separated (for Angular): no
  • Exception message and full stack trace: Not really required.
  • Steps to reproduce the issue: There's too much to list, however, I've been working with ABP all-day long trying to resolve an issue with Abp Suite. When I created two entities, SpecialtyBreed and CommercialBreed, I added two properties. They are BreedName and Description. During CRUD generation the Description property never made it into the IXXXRepository and cause many issues, including with the tests. I also had the same issue with adding a property name "Photo" which was a string property.

I've cleared the OBJ and BIN directories, closed/reopened Visual Studio and no luck. Also, going back to version 8.0.0 I have an ENUM in the Domain.Shared/Enums. I can't even use it because the generated code is looking for the Enum in ApplicationName.Shared.

Hey Team, I have a question for all of you. I have previously created my database which contains linking tables. Am I able to utilize ABP Suite to maintain my data schema? If not, what is the recommended way to implement linking tables in the ABP Framework?

  • ABP Framework version: v8.0.1
  • UI Type: Blazor WASM
  • Database System: EF Core (SQL Server)
  • Tiered (for MVC) or Auth Server Separated (for Angular): no
  • Exception message and full stack trace: N/A
  • Steps to reproduce the issue: N/A

I’m trying to add a module to my Blazor server solution based off of the Application Template. My primary solution is NexusSystems and the module I’m trying to add is NexusSystems.BinManagement. I’ve installed Redis on WSL, however, when I check the box to add to solution I receive a permissions error to the Application.Context.dll for the module. I had the solutions in the c:\Users\username\source\repos and then moved to the public docs as well as unchecking the read only box under folder properties, still no luck.

  • ABP Framework version: v8.0.1
  • UI Type: Blazor Server
  • Database System: EF Core (SQL Server
  • Tiered (for MVC) or Auth Server Separated (for Angular): yno
  • Exception message and full stack trace: Permission to NexusSystems.BinManagement.Application.Contrxt.dll Denied
  • ABP Framework version: v7.4.0
  • UI Type: Angular
  • Database System: EF Core (SQL Server)
  • Tiered (for MVC) or Auth Server Separated (for Angular): no
  • Steps to reproduce the issue:
  1. Create a new Angular project with MAUI.
  2. Perform all required pre-run steps, including seeding of the database.
  3. Run the application to assure it works and you're able to login.
  4. Now, utilizing Abp Suite create a new entity name GrowthRate and use the following properties:
    1. Girth - Datatype as double with min value of 0 and max value of 999 and non-nullable.
    2. Weight - Datatype as double with min value of 0 and max value of 999 and non-nullable.
    3. Length - Datatype as double with min value of 0 and max value of 999 and non-nullable.
    4. AssessmentDate - Datatype as datetime non-nullable.

Once that has been completed your build should fail when you attempt to run it. As you can see from the attached image the values are trying to use a Date Datatype.

  • ABP Framework version: v7.3.3
  • UI Type: MAUI BLAZOR
  • Database System: EF Core (SQL Server)
  • Tiered (for MVC) or Auth Server Separated (for Angular): NO
  • Exception message and full stack trace:
  • Volo.Abp.AbpInitializationException: 'An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module Volo.Abp.AspNetCore.Components.MauiBlazor.AbpAspNetCoreComponentsMauiBlazorModule, Volo.Abp.AspNetCore.Components.MauiBlazor, Version=7.3.3.0, Culture=neutral, PublicKeyToken=null: An error occurred during the ABP remote HTTP request. (Failed to connect to localhost/127.0.0.1:44321) See the inner exception for details.. See the inner exception for details.'
  • Steps to reproduce the issue:
    1. Create a new MAUI BLAZOR project.
    1. Seed database.
    1. Set startup projects to Api.Host and MAUIBlazor.
    1. Attempt to run using Android emulator.

I've spent all day yesterday trying to get this to work and was unable to do so. I did have ngrok also setup in the MAUI Blazor application which didn't make any difference. I have double and triple checked I have all requirements to run .MAUI installed. If I create a new MAUI HYBRID project from VS it works just fine. I thank you in advance for helping with this.

Showing 1 to 6 of 6 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06