Activities of "cfd000"

• Steps to reproduce the issue: Compile ABP open source framework while targeting SixLabors.ImageSharp version 4.0.0 or higher, and an error will tell you that a license file is required.

https://sixlabors.com/posts/licence-enforcement-changes/

Is there a plan to migrate away from SixLabors? Cost - I don't begrudge them needing to earn money from their work product, but our work product is not yet revenue generating and we have hundreds of dependencies, paying them all is not possible.

Licensing - Their license is complicated and makes it challenging for us to prove we are in compliance, especially since we try to build as much of the project as we can internally rather than rely on packages for everything

https://abp.io/support/questions/8530/Uncaught-TypeError-leptonxmobileNavbarcloseMenu-is-not-a-function

This issue is still happening, although it says that it was fixed 2 months ago. There is no information in the ticket explaining a workaround, or what version to expect the fix in. I have tried creating new projects using 9.0.5 and also updating to 9.1.0-rc.2 and both still give me the same error.

What is the status of this ticket, and how do I get a fix or workaround right now?

We have always used fewer questions than we are allotted. Our subscription renewed about 2 months ago. Why does the counter say we have used 79 questions? I am only counting 5 (2 from me, and 3 from spospisil).

• ABP Framework version: v9.0.3
• UI Type: Blazor WASM
• Database System: EF Core (PostgreSQL)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Exception message and full stack trace: 2025-01-13 18:14:03 [23:14:03 ERR] ABP-LIC-ERROR - License check failed for 'Volo.Abp.AspNetCore.Mvc.UI.Theme.Commercial-v9.0.3.0'. 2025-01-13 18:14:03 You need to log in using the command abp login <username>. 2025-01-13 18:14:03 For more information, contact to license@abp.io.
• Steps to reproduce the issue: Create a new solution using ABP CLI, and configure it to run using docker compose. Under older versions of ABP we would put the "access-token.bin" file in /root/.abp/cli in the Docker container using the following code:

COPY ["../StructureCloud.NET/access-token.bin","/root/.abp/cli/"]
RUN chmod -R 777 /root/.abp/cli/

This used to work fine. Under ABP 9.0.3 and .NET 9, this no longer seems to work.

I tried using the contents of the access-token.bin file as a value for an environment variable named "AbpLicenseCode" but that did not work.

Based on other posts I have found (I did not find any documentation stating that a change was made), I tried adding an environment variable based on the appsettings.secrets.json that was created. - AbpLicenseCode=PAB...

I am now getting different errors in each container. AuthServer: "ABP-LIC-ERROR - License check failed for 'Volo.Abp.AspNetCore.Mvc.UI.Theme.Commercial-v9.0.3.0'" HttpApi: "ABP-LIC-ERROR - License check failed for 'Volo.Abp.LanguageManagement.Domain-v9.0.3.0'" WebPublic: "ABP-LIC-ERROR - License check failed for 'Volo.Abp.LanguageManagement.HttpApi-v9.0.3.0'"

Why was this changed, why wasn't it documented, and what is the procedure to make it work?

DO NOT tell me to use PRODUCTION mode, I am doing development in VIsual Studio using Docker Compose, and this is the development environment.

• ABP Framework version: v8.3.1
• UI Type: Blazor WASM
• Database System: EF Core (PostgreSQL)
• Tiered (for MVC): yes

What is the recommended way to create a new solution and incorporate all ABP source code using the CLI? This should include the base framework as well as any module source required (both open source and PRO modules).

We have a license for ABP Commercial with includes full source code. Any time we have needed to make a temporary modification or fix to the source (could be a breaking change, an immediate need to reference an updated NuGet package with a security update, etc.), it is too time consuming and error prone to switch from packages to source, so we must build our production release from full source to begin with. We would like to use the CLI so that we can script it and reuse the code for each major release (create a new clean ABP solution, validate that it builds, then bring over our changes from the prior version).

• ABP Framework version: v8.3.1
• UI Type: Blazor WASM
• Database System: EF Core (PostgreSQL)
• Tiered (for MVC): yes
• Exception message and full stack trace: "Unable to satisfy conflicting requests for 'Volo."
• Steps to reproduce the issue: Create a new solution using CLI referencing packages - it will compile. Switch to local source, and now the same project throws many compile errors about conflicting requests. The same thing happens when downloading source for modules. They compile until the CLI option to use local source is run.

• ABP Framework version: v7.2.2
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes

* **Exception message and stack trace**: C:\Users\chris\.nuget\packages\microsoft.build.tasks.git\1.1.1\build\Microsoft.Build.Tasks.Git.targets(25,5): warning : Unable to locate repository with working directory that contains directory 'D:\Blazr4722\abp\framework\src\Volo.Abp.Core'. [D:\Blazr4722\abp\framework\src\Volo.Abp.Cor
e\Volo.Abp.Core.csproj]
C:\Users\chris\.nuget\packages\microsoft.sourcelink.common\1.1.1\build\Microsoft.SourceLink.Common.targets(53,5): warning : Source control information is not available - the generated source link is empty. [D:\Blazr4722\abp\framework\src\Volo.Abp.Core\Volo.Abp.Core.csproj]

• Steps to reproduce the issue:" Create a new solution which references local source code:

abp.exe new MyNewProject --template app-pro --ui blazor --pwa --database-provider ef --database-management-system PostgreSQL --mobile maui --separate-identity-server --separate-tenant-schema --tiered --with-public-website --no-random-port --local-framework-ref --abp-path ..\..\..\ --version 7.2.2 --output-folder D:\Blazr4722

Fix all references to 'licensing' projects, so that the solution will actually compile https://support.abp.io/QA/Questions/5140/New-Solution-Does-Not-Compile

Go to the solution directory and run dotnet build

You will receive hundred of errors related to Source Link

• ABP Framework version: v7.2.2
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace: error CS0234: The type or namespace name 'SuiteTemplates' does not exist in the namespace 'Volo.Abp.Commercial' (are you missing an assembly reference?) error CS0246: The type or namespace name 'VoloAbpCommercialSuiteTemplatesModule' could not be found (are you missing a using directive or an assembly reference?)
• Steps to reproduce the issue:"

abp.exe new MyNewProject --template app-pro --ui blazor --pwa --database-provider ef --database-management-system PostgreSQL --mobile maui --separate-identity-server --separate-tenant-schema --tiered --with-public-website --no-random-port --local-framework-ref --abp-path ..\..\..\ --version 7.2.2 --output-folder C:\Src\MyNewProject

Create a new ABP solution which references source code. The solution will contain a number of references to projects in the 'licensing' folder, which is not part of the source code which is made available. The new solution will not build successfully until all of these project references have been changed to package references.

We have had to write scripts to process the 831 projects that result (download of source framework, plus Pro modules, plus the new project which was created), and parse all references, removing references which contain 'licensing' and replacing them with package references.

This should not be necessary. Since the 'upgrade' command has not worked well for us in the past, we are creating a new ABP solution each time a new version is published, and moving our changes in to that new version. This extra work also is a barrier to new companies trying to use ABP for the first time.

• ABP Framework version: v6.0.0
• UI type: MVC / Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes

According to Microsoft documentation, System.Net.Mail.SmtpClient is obsolete and should not be used.

• https://github.com/dotnet/platform-compat/blob/master/docs/DE0005.md
• https://github.com/dotnet/dotnet-api-docs/issues/2986
• https://learn.microsoft.com/en-us/dotnet/api/system.net.mail.smtpclient?view=net-6.0

Additionally, Office 365 is going to disable basic authentication for SMTP as of December 31, 2022. https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online

All of the documentation indicates that MailKit https://github.com/jstedfast/MailKit is now the recommended solution.

I did not see a way to use OAuth2 with MailKit using the ABP module. Is there any sample code that demonstrates how to do this?

• ABP Framework version: v6.0.0
• UI type: MVC / Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes

We are slowly replacing the UI for a very large existing application with ABP, and are happy to have the Auditing capabilities. Some entities may be completely controlled (created, updated, and deleted) by the legacy application for quite a while as we work on building out different areas using ABP. We would like to enable Audit Logging for changes to certain tables that are NOT being modified through ABP (although they will be in the same database as the ABP tables). Do you have any suggestions on how to write the appropriate audit log entries for changes made outside of ABP? The legacy application will be doing direct SQL edits, so we are thinking of tracking those changes using triggers.