Hi @BradAdler,
Collection names
filed doesn't exist in v5.3.3
.
I guess you need to type Users
in Collection name
filed.
Hi @john,
We've fixed the issue. Thank you for reporting.
Question credit is refunded.
Hi again,
I inspected the code and you are right. It will be fixed in the stable release.
Hi @barrett2474,
You can use -p
parameter in the command.
ex: abp login <username> -p <password>
Hi @mateworkx,
Did you build your solution after upgrading?
If not, build it and restart ABP Suite.
What @Sumit
abp.message
doesn't support html rendering.
You can directly use SweetAlert2 (that abp.mesage
uses too).
https://sweetalert2.github.io/
Hi @MrShadowland,
Open %UserProfile%\.abp\suite\appsettings.json
file in your computer.
There you will see the list of solutions you added to ABP Suite. You can find the solution you mentioned and change DbContextFilePath
and DbContextModelCreatingExtensionsFilePath
values.
However, i can not guarantee that it will work with of your custom AppDbContext.cs
file content. But you can try.
It looks like the fourth attempt was different in some way and worked. But the first 3 attempts for this package failed.
It doesn't do anything different in the 4th attempt. So it is probably a network related issue.
Hi @scott7106,
Please update CLI to preview version.
dotnet tool update -g Volo.Abp.Cli --version 6.0.0-rc.3
Hi @zhaof,
Can youtry to re-install abp-suite?
abp suite remove
abp suite install -v 5.3.4