Activities of "ezarmer"

The 2 biggest issues I have with the support are: One line answers with no explanation or details. For example: "Add an override to the X method" and then a link to code on GitHub Similar to item 1, single line responses that are a link to documentation that doesn't answer the question and in most cases we've already read.

Bare-minimum support is to provide a link to documentation. Don't do the bare minimum only.

World-class support attempts to understand what the user is asking and provide a slightly more in-depth answer, an example, or short code snippet. Strive to be world-class.

Speaking of documentation. Either keep up with your documentation or hire a technical writer to do that. Documentation in general seems to be outdated.

For me personally, it should not matter where support comes from. Being told on Discord that I must ask my question via the support website is, well, frankly rude and unprofessional. If the community can help answer questions then it takes some burden off of the support team. So, why wouldn't you want this?

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

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.

I will send the compressed zip file to support via email.

May I have a status update on this please?

Thank you for the reply.