The old CLI is legacy, and we are not adding any new features. This version is for the ones who have old ABP projects and don't want to upgrade (basically for backward compatibility). You need to use the new CLI and Studio.
Where did you see the recommendation to use the old CLI version?
I updated my Studio and Suite to the latest
And I couldn't see any errors like versions conflict etc...
can you pls check it with the latest version @improwise
the latest Studio creates ABP 8.3.1 projects
Why start template not published when a new version released?
it is a long time can not get the template 8.3.1 after it released, abp cli and abp studio also upgraded to latest version.It seems like something weird is going on with the CLIs, see my other posts above. ABP needs to comment on this. Short version seem to be that in order to use latest version of ABP, we need to stop using ABP Studio and the new CLI and return to old CLI and ABP Suite. This assuming you can still actually create new versions in that with the old CLI installed. If not it seems we are back to only using the old CLI to create new solutions with the latest version of ABP :)
Edit:
Just tried to create a new solution with ABP Suite having only the old CLI installed (8.3.1) and you can only add existing solutions, not create new ones. Creating it using the old CLI you can then add it to ABPU Suite it seems, but perhaps not ideal DX.
@improwise Sometimes I respond to the feedback, sometimes not. But I'm reading all the feedback and reporting to the team.
You can report bugs and issues under this topic, and for the Feature / Enhancement Requests you can write under https://abp.io/support/questions/3052/this topic
you need to enter the username, not the email address. that's why you cannot find the corresponding user.
and his username is zizooo.elhor
ok then we'll look deeper into this issue
When you enable the Dynamic Claims feature, in each request, we read the claims (from Redis) of the request to check current permissions in the current session. If you disable it, when you revoke permission from a user, he needs to log out / log in to refresh his permissions.
I think your IIS problem is related to invalid SSL certificate and @maliming solved this issue. Can you open a new question if you ask another topic?
@liyingji publishing an ABP web application to IIS is almost same as publishing any ASP.NET Core Web application to IIS. There's no extra diffucdifficulty for ABP solution. Even you publish a simple ASP.NET Core application, you will see the same problems. But @maliming will try to help you to find your envenvironmental problem. And once you fix it, share your problem here, so everyone will see it and get benefit from this experience.
