ensure that https://localhost:44325 is accessible. sometimes Visual Studio kills the IIS Express
check out https://docs.abp.io/en/abp/latest/Background-Workers-Quartz
@prasad.gore do you see a valid response from https://localhost:44325/api/abp/application-configuration
to implement this you can add a new property to your tenant entity like TenantType and you can overwrite the tenant creation method so that you force your logic before the creation. You check the tenant type and decide if the current user (or role) can operate on this.
this is a broad implementation. better to filter down your problem into smaller ones so I can write specific solutions.
Maybe Blazor didn't implement this because it runs in your browser. Also Blazor is a client and you also have a host. So these projects have different versions. The best practise is storing Blazor client version in a const variable and get the host version via API call. Create a new application service like ApplicationInfoAppservice and return the version from this service...
is your host is up and running? check https://localhost:44325
@l.lemmens thanks for reporting, we'll check that.
@lszabados do you want to add a summary desc for your properties? and do you want to see that summaries only on the entity?
@james :
I created a new Microservices project using ABP Suite. When I add a new Tenant, regardless of the username and password entered, the Save action always produces "admin@abp.io" with the standard password.
When I create a standard Application (monolith), the action works as expected.
BTW, the 4.2.0 update is awesome! Keep up the fantastic work.
yes, this is a known bug and the team is working on this issue. this will be fixed in v4.3. as a workaround, you can update the new user credentials manually.
@michael.sudnik:
When will 4.2.1 be released? We need the fix for the modals within modals.
Today