Activities of "jermaine.gray@gmail.com"
I already switch from blazer to MVC and delete the blazer project. am not having this problem with MVC. so you guys need to create blazer project and you will see the problem.
am coming back to this point. I dont think it is the IDE not copying files. when i used .net publish cli the app publish but it seam it missing some critical file
Volo.Abp.AbpInitializationException: An error occurred during ConfigureServicesAsync phase of the module Volo.Abp.AspNetCore.Components.Server.AbpAspNetCoreComponentsServerModule, Volo.Abp.AspNetCore.Components.Server, Version=9.0.1.0, Culture=neutral, PublicKeyToken=null. See the inner exception for details.
This indication that there is problem getting the statice file ---> System.IO.DirectoryNotFoundException: C:\Users\xx.nuget\packages\volo.abp.aspnetcore.components.web\9.0.1\staticwebassets\
I also notice some dependence issues within the blazer app
Am trying to publish my app on MS Azure
It looks like it works, but I am going to upload it to the server first. Is there a bug in Visual Studio why the publish button does not work?
no abp studio or any part of my app was not running
I appreciate the opportunity to test your product, but I must express my dissatisfaction with its current state. Here are my key concerns:
Refund Request: The cost of this product is too high for me to act as a tester. If known issues exist, such as unsupported features, the product should not have been released in its current form. I request a refund to my question.
Compatibility Issues: All of my projects use MySQL, and the lack of support for this database is a major limitation. Should I wait for a fix, or can I create a project with a different version? Clarity on this is essential.
Long-Standing Bugs: I encountered a bug in Swagger related to MIME type mismatches:
The resource from “https://localhost:44394/swagger/ui/index.js” was blocked due to MIME type (“”) mismatch (X-Content-Type-Options: nosniff).
This issue has reportedly been around for over five years. Releasing a product with unresolved, long-standing bugs like this is unacceptable.
These issues collectively make it difficult for me to continue using the product effectively. I strongly recommend prioritizing fixes and better communication around unsupported features before further releases.