ok I found the reason. This happens when your ABP CLI version and the project version you are generating is different. In my case, ABP CLI is 7.0.0-rc.5 and I'm generating 6.0.2 project, this makes the error. Install ABP CLI 7.0.0-rc.5 and create a new rc.5 project.
update to the latest preview
dotnet tool update -g Volo.Abp.Cli --prerelease
abp suite update --preview
new project
abp new abptest7 --theme leptonx -ui blazor --version 7.0.0-rc.5 -csf
so keep the CLI and the project version same
Hey @swnke2,
I'm checking it, and I confirm that I get this error here
assigned @enisn to your issue, and he'll write you about the solution.
on the other hand, don't worry about the trial expiration; we'll help you with that.
this is the default setup of the Logger. You can customize it according to your requirements.
If your pen test tool raises it as a "low level security leak" you can change it in the src/TaajeerFinance.HttpApi.Host/Program.cs class. Set it to .MinimumLevel.Fatal() .
We cannot do it in the framework because it's not in the framework. It's in the application that you have generated.
@andmattia I think you should keep your several issues on a single thread. I see you have similar questions via email and support.abp.io. each time the support team asks you new questions to understand your setup. please keep it in a single question so that we can help you better
ok I can confirm that refresh_token is not available right now. we'll respond you about this issue asap
ok. I'll check this
did you manage to find a way for this, or are you still waiting for assistance?
Dynamic Permission feature is implemented with this PR https://github.com/abpframework/abp/pull/13644 @maliming will try to help you with that.
you may have a general problem resolving the tenants. to be able to use Swagger you can use cookie authentication.
Hello. Sorry for the late response. I tried some other methods. In the end, i tried inserting the highlighted lines in the first picture into the code. Doing so generated the result in the second picture.
@Anil, no need to do this.
Create your own DataSeeders, these will run one by one (not random)
also you can create a new empty EF Core migration dotnet ef migrations add MyNewMigration. And write your SQL inserts here in the empty migration file, write T-SQL inserts...
public partial class Insert_Into_MyTable : Migration
{
protected override void Up(MigrationBuilder migrationBuilder)
{
migrationBuilder.Sql(@"INSERT INTO MyTable .....");
}
}
