Activities of "tuk"

• ABP Framework version: v8.2.0
• UI Type: Blazor Server
• Database System: EF Core (MySQL)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace:
• Steps to reproduce the issue:

Hello To support a Legacy system we need to change length of Name and NormalizedName in SaaS module. Table "SaasTenants".

According to documentation it says: /* You can change max lengths for properties of the

• entities defined in the modules used by your application.
• Example: Change user and role name max lengths AbpUserConsts.MaxNameLength = 99; IdentityRoleConsts.MaxNameLength = 99;*/

I have identified following in SaaS module: Volo.Saas.TenantConsts.MaxNameLength

However this is a constant and cannot be changed.

What would be the correct (best) implementation to change the length of a field in SaaS module so it will reflect all the way up to UI?

Hi Got it now, thanks.

I think you misunderstand. In 8.2.0, there are new tables, how do I get the migration file to generate those tables? I have no files in my folder after fetching new version I only have a initial file with all table creation. But I already have a DB so I just need the changes from 8.1.4 to 8.2.0. For example in ASP.Net Zero you provide migration files for each update.

So you do not provide the migration code files to upgrade from 8.1.4 to 8.2.0 I should figure out all changes myself and create migration files manually?

I have this in my migration folder after updating to 8.2.0, how to apply new migration relevant to 8.2.0?

I mean how to generate the migration code to update DB to new schema used with 8.2.0?

• ABP Framework version: v8.1.4
• UI Type: Blazor Server
• Database System: EF Core (MySQL)
• Tiered (for MVC) or Auth Server Separated (for Angular): no

Hello We just started a new project on 8.1.4 a few weeks ago, and now we need to update to 8.2.0. However we do not find any easy way to do the DB migration.

We expected there to be new migration steps to apply, but instead we just get one big initial migration, which will not work on an existing DB.

How do we obtain the delta migration steps (8.1.4 to 8.2.0) to apply to our DB?

We have searched documentation, but did not find anything on how to do this.