Activities of "yekalkan"

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.

Hi @darutter,

As i see it, Guid and Char are especially disabled for Blazor projects. I researched the reason and found this explanation:

Blazorise components doesn't have char data type, so we should hide it if the UI is Blazor.
Also remove Guid because there's no component for Guid type

This was a year ago. I'll create an internal issue and re-consider enabling them.

Hi,

Can you share the build error when you run "dotnet build" on the solution?

Hi @Mikael,

Is a "Name" property mandatory?

No, it shouldn't be. Probably there is a bug, so i refund your question credit and we will fix it in next release.

For now, you can just replace the Name with the real display property name manually in EditModal.cshtml file and it will be OK.

https://github.com/abpframework/abp/pull/12226

Hi @jhsanc,

I didn't mean it will solve the issue completely.

This will be fixed in next patch version (v5.2.1) soon.

Fyi: You can delete CreateMap<InscriptionTypeCreateDto, InscriptionType>()... and CreateMap<InscriptionTypeUpdateDto, InscriptionType>()... lines completely.

Hi @jhsanc,

Thanks for the report. I created an internal issue & refunded your question credit.