Please update release notes BEFORE publishing a new release The new version of abp studio is 0.9.3, but what problems does it solve?
https://abp.io/docs/latest/studio/release-notes
https://abp.io/docs/9.0/studio/release-notes
I installed the update and now I have this error, why?
And Abp Suite does not start.
I rollback to Abp Studio 0.9.2, waiting for news.
Thanks
Add **SMTP OAUTH ** in Infrastructure Service https://abp.io/docs/latest/framework/infrastructure/emailing or add a guide to configure MailKit to use SMTP OAUTH https://abp.io/docs/latest/framework/infrastructure/mail-kit
See Microsoft's announcement https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-to-retire-basic-auth-for-client-submission-smtp/ba-p/4114750
Thanks
With the latest version of abp studio (0.9.1) I can't create a version of ABP 8.3.2. It always creates version 8.3.1
When will the new version of abp studio be released that supports the new abp release?
Can you find a solution so that when a new version of ABP is released, the version of abp studio that supports it will be released almost at the same time?
Thanks
Hi! We have no 8.3.0 version for Volo.Abp.Studio.Cli. You can view version compatibility from this document: https://abp.io/docs/latest/studio/version-compatibility
We haven't released a version for 8.3.0 packages yet. We will after we finish our controls. For now, if you want to use 8.3.0 version packages for your Studio templates, you can easily upgrade your packages from here:
Hi @EngincanV, in your first post the command "dotnet tool update -g Volo.Abp.Studio.Cli --version 8.3.0" is wrong. Version 8.3.0 is for Legacy CLI and not for Abp Studio.
Hi @oyku.erman, When will abp studio support abp 8.3.0? And when https://abp.io/docs/latest to "8.3 (lastest)" ?
Since VoloSoft is pushing to use Abp Studio I expected that with the release of a new version of ABP after 1 or 2 days we would have everything aligned.
I ask you for an extra effort because the use of abp studio in our work workflow should be transparent and today instead it is creating delays due to understanding what has been fixed and what has not.
This will be even more evident with the preview that uses .Net 9
Thank you for your commitment.
With the latest version of abp studio (0.7.9) I can't create a version of ABP 8.3.0. It always creates version 8.2.2 even if the stable version is 8.3.0
Why?
Please update the contents of the page RoadMap
https://docs.abp.io/en/commercial/latest/road-map#backlog-itemsThis page should also be updated
https://docs.abp.io/en/commercial/latest/aspnet-zero-vs-abp-commercialSo, we can understand what the next releases will be.
Example, when will this feature be implemented?
Thanks
2 months later, the Road map page is still severely outdated, claiming that 8.2 will be released in June
https://abp.io/docs/latest/release-info/road-map
the road map is already updated
Thanks for updating the page yesterday.
I wanted to know if there are any updates on the implementation of Real time notifications.
Thanks
Latest version now gives this error (assuming it is trying to use mkcert without installing it)
Some pre-requirements are missing. If you want the application to work as expected, you need to install the following tool(s):
- mkcert. (Installation link: https://github.com/FiloSottile/mkcert)
If you have already installed the tool(s), please check the PATH environment variable.
As seen in the error message, we're using the
mkcert
command during the solution creation process. So you should downloadmkcert
by following the installation guide.
@ahmetfarukulu Why don't you use the dotnet tool? https://learn.microsoft.com/en-us/dotnet/core/additional-tools/self-signed-certificates-guide
Ok, thanks
Sorry, one last question. Since it is done: ApplicationConfigurationChangedService.Changed += ApplicationConfigurationChanged;
I should make a Dispose method with: ApplicationConfigurationChangedService.Changed -= ApplicationConfigurationChanged;
What is the correct way to write the Dispose method of the component?
It's an acceptable workaround. If I have other problems I will open a new ticket. Thanks