Thank you for the reply.
May I have a status update on this please?
I will send the compressed zip file to support via email.
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'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.
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?
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.
One thing I would like personally is a notice that the ticket investigation has started, or even has been seen, on a post.
I've seen one ticket today that's over 9 days old without even initial feedback on it, just a chaser by the OP.
I've logged a P1 ticket for us today as we can't do any work with the feed out, but no idea if it's even been seen by the support team.
I agree with you. It would be nice to know that someone has acknowledge the fact that we've posted a ticket.
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?
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.
