Base solution for your next web application

Activities of "maliming"

@csbeginner Sorry my English reading ability is not very good.

ConcurrencyStamp and SecurityStamp are GUID strings. sql is NEWID()

  1. You can write a special interface for importing users in bulk. According to the user data of TableOnAnotherApp, the user information (such as username, email, password, etc.) needed by the current application is constructed. Internal use of _userManager.CreateAsync. The framework will automatically handle other User attributes.

  2. If you want to use sql insert statement, please set a string password, bypass sql constraints, and then write a loop in the application to query the imported user, and then set a new password for them.

You can disable the IMustHaveTenant and IMayHaveTenant with a using statement filters after switching to the host.

detailed explanation: [https://www.aspnetboilerplate.com/Pages/Documents/Multi-Tenancy#switching-between-host-and-tenants])

Version 5.5 is the release version. Dev Branch is the latest development code.

The reason why it is bulky is because it contains git records and some objects needed for development.

Just like the documents says: [https://www.aspnetboilerplate.com/Pages/Documents/Entities#iextendableobject-interface])

IExtendableObject defines the ExtensionData string property which is used to store JSON formatted name value objects.

So it can store any object that can be serialized into json

While this technique can be very useful in some cases (when you need to provide the ability to dynamically add extra data to an entity), you should normally use regular properties. Such dynamic usage is not type safe and explicit.

Can you share the complete stack information?

You can try to modify the database name of the database connection string, re-migrate and start the application to see if it is still wrong.

Is the primary key id of the data in the Abp Tenants table a number 1?

If you are just starting the project, you can delete the database and re-migrate.

You can allow the user to bind the phone number when logging into the application after the user has successfully registered.

:D

For security and privacy reasons, I believe that applications cannot get sensitive information unless they are actively provided by the user.

Showing 2971 to 2980 of 2993 entries