Hi, we notice that the appsettings.secrets.json gets publish too - and deleting it cause a "ABP-LIC-0020". How to we prevent this sensitive information from deploying to our clients ? ( microsoft states that you should not use any secrets file outside the development process )
Beside, is there any documentation about how to publish abp correctly ? well the process is pretty much straight forward but the secret should not be contained in output. some advice about how to publish the migration project within the blazor project ( to prevent duplication of dll's ) and run it automaticly on blazor start would be great :)
Thanks
it works with server.LeptonXTheme and Theme.LeptonX 1.0.4
added
<PackageReference Include="Volo.Abp.AspNetCore.Components.Web.LeptonXTheme" Version="1.0.4" />
to our main Blazor project
now i get _Host.cshtml(5,42): Error CS0234 : The type or namespace name 'LeptonXTheme' does not exist in the namespace 'Volo.Abp.AspNetCore.Components.Web' (are you missing an assembly reference?)
also the nuget manager shows:
there are no v1.0.4 for UI.Theme.LeptonX and Components.Server.LeptonXTheme - not sure if this is correct
create SideMenuLayout.razor in Components/ApplicationLayout with the content you posted but it is not used
so please, just create a new package version...
@EngincanV this doesnt work... how can i override the file with only the part you provided ? please create a backport or share the full SideMenuLayout.razor file. thanks note: if you dont want to share this in puplic, sent it to my email - but that wont solve the problem for all other people that need to stay on net 6 too
well, it reference v7 packages and require net 7 - so we cannot update to it.
Package Volo.Abp.AspNetCore.Components.Server.LeptonXTheme 2.0.0 is not compatible with net6.0 (.NETCoreApp,Version=v6.0). Package Volo.Abp.AspNetCore.Components.Server.LeptonXTheme 2.0.0 supports: net7.0 (.NETCoreApp,Version=v7.0)
@EngincanV will there be a v6 release for this fix ?
ok thanks
@christianharoh abp suite will do this for you, just check "Separated tenant schema", details can be found in thedocumentation
well, you cant implement IIdentityDbContext without IdentityClaimType and IdentityLinkUser
