Hi @mittera,
We are committed to continuously enhancing Asp.Net Zero and Power Tools, driven by our goal of constant improvement. We greatly appreciate the ideas and requests we receive from you, as they play a crucial role in shaping our products. Your suggested idea holds tremendous value, and we will carefully discuss and evaluate it. We sincerely thank you for your valuable feedback, and any decisions made will be based on a collective assessment.
Hi @omkarchoudhari,
We recommend updating to the latest version as some of the alerts mentioned here might have been resolved in subsequent releases. In the current version, we will assess the headers and identify any missing headers that need to be included in the upcoming version.
Hi @ictadmin,
I couldn't reproduce the issue. Could you share your project with [email protected] ?
Hi alexanderpilhar,
Could you update your project to the next version? It seems fixed here https://github.com/aspnetzero/aspnet-zero-core/issues/4718
Hi @attspacecom,
You can name constraint names manually like this answer https://stackoverflow.com/a/64527547.
Hi InnodelTech,
Could you share your project with us at [email protected]
Hi @InnodelTech,
I think it is not related to AspNetZero Rad Tool. I tried with a fresh solution and I couldn't reproduce the errors. There is an error at DbContext. Could you fix this and regenerate entities?
Hi @Leonardo.Willrich,
I couldn't reproduce it in a new solution. Could you download a new solution and compare it with yours?
Hi, you can hide your framework by removing the scripts below at abp.js
"abp.timing.utcClockProvider", "abp.aspnetboilerplate.version"