Activities of "yekalkan"

Be sure that installed ABP Suite version is same.

Also, Can you share the OnModelCreating method in SaasServiceDbContext?

Hi @mhdbazcashin,

Suite doesn't support code generation on AdministrationService, IdentityService & SaasService.

However, we are planning to support them as well in future versions.

Btw,

Have you set your Trial license organization as default in https://commercial.abp.io/my-organizations page? If so, please change it to the actual organization.

The logs are the same.

Can you share them?

Are you sure the Suite is installed currently?

abp-suite should be available after you run abp suite install.

Fyi, you can fix it by this convertion in column definitions in index.js file:

eXMailbox > exMailbox eXGroup > exGroup

Does it crash when you run abp-suite command instead of abp suite?

Hi @shobhit,

When Using CRUD Page Generator Angular UI is not getting generated even C# code is getting generated

There is a known issue that causes angular ui generation to fail, when there are spaces in the solution folder path. (ex: C:\my projects\Acme.BookStore)

May it be the same for you?

Run ABP Suite. Below error occures. As yes we have valid license.

There is a file named %USERPROFILE%\.abp\suite\suite-license.bin in your environment. Can you open it with a text editor and tell me if it looks ok? Also, when you started to get this error?

Hi again,

Problem is be fixed in and will be released in the next patch release. To fix it in 5.1.4, follow these steps:

• Create appsettings.json & appsettings.secrets.json files under test\Volo.Saas.TestBase\Volo\Saas folder.

appsettings.json content:

{

}

appsettings.secrets.json content:

{
  "AbpLicenseCode": "Your Abp License Code"
}

(You can find your license code in the main solution. Just copy from there.)

• Add the following configuration to test\Volo.Saas.TestBase\Volo.Saas.TestBase.csproj file:

  <ItemGroup>
    <None Remove="Volo/Saas/appsettings.json" />
    <Content Include="Volo/Saas/appsettings.json">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
      <ExcludeFromSingleFile>true</ExcludeFromSingleFile>
      <CopyToPublishDirectory>PreserveNewest</CopyToPublishDirectory>
    </Content>
    <None Remove="Volo/Saas/appsettings.secrets.json" />
    <Content Include="Volo/Saas/appsettings.secrets.json">
      <CopyToPublishDirectory>PreserveNewest</CopyToPublishDirectory>
      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
    </Content>
  </ItemGroup>

• Add the following configuration to ConfigureServices method in test\Volo.Saas.TestBase\Volo\Saas\SaasTestBaseModule.cs file:

        var builder = new ConfigurationBuilder();
        builder.AddJsonFile("Volo/Saas/appsettings.json", false);
        builder.AddJsonFile("Volo/Saas/appsettings.secrets.json", true);
        context.Services.ReplaceConfiguration(builder.Build());

(you may need to add Microsoft.Extensions.Configuration namespace)

Hi @Mikael,

I don't know if there is any documentation specifying that we cannot use double uppercase at the beginning of the entity name... ?

No, we don't have such restriction. This is probably related with a differency between camelCase convertions.

I'll create an internall issue and fix it asap. Thank you for reporting, your question credit is refunded.