according to the license rules, paid modules cannot be provided as open-source. as an example, you can purchase the full-source code of ABP Commercial and add a little value on top of it and make it open-source. So the complete commercial project becomes open-source. I hope it's clear now.
1-run the below command in CMD (clears your current login session):
del %UserProfile%\.abp\cli\access-token.bin && del %UserProfile%\.\AppData\Local\Temp\AbpLicense.bin
2-login again:
abp login <username> -p <password>
3-run Suite to try again:
abp suite
Running your project in Docker container:
ABP makes online license check only in Development environment or when the Debugger is Attached in Visual Studio.
When it's in Development environment or Debugger is attached, it's required to login your account via ABP CLI ( abp login {username} )
When you run your app in a Docker container, publish it in Release mode. Set your environment as Production to skip online license check (or anything else other than Development) using the following command:
-e "ASPNETCORE_ENVIRONMENT=Production"
If you are required to run the project in Development environment in the container, copy your local ABP token file %UserProfile%\.abp\cli\access-token.bin into the Docker container's relavant directory.
By relavant directory, it's meant to be the current user's home directory.
%UserProfile%\.abp\cli\/home/user/.abp/cli/If you get the following error, you probably logged in 2 different computers and trying to login in the 3rd unique computer.
In this case, send an email to license@abp.io to reset your linked computers.
License Error! Given user 'XYZ' has reached the maximum allowed developer computer count (2)
If you face with one of the following problems:
abp login <username>.@AlderCove we couldn't reproduce it. can you create a new question, seems like it'll be being discussed (not to bother others)
according to the Microsoft docs it supports SqlParameters
https://docs.microsoft.com/en-us/dotnet/api/microsoft.entityframeworkcore.relationaldatabasefacadeextensions.executesqlrawasync?view=efcore-5.0#Microsoft_EntityFrameworkCore_RelationalDatabaseFacadeExtensions_ExecuteSqlRawAsync_Microsoft_EntityFrameworkCore_Infrastructure_DatabaseFacade_System_String_System_Object___
To update your version to the latest (v4.2) for both ABP CLI and ABP Suite run the following command
dotnet tool update -g Volo.Abp.Cli && abp suite update
v4.2 Preview Version Notes https://blog.abp.io/abp/ABP-IO-Platform-v4-2-RC-Has-Been-Released
v4.2 Final Version Notes https://blog.abp.io/abp/ABP.IO-Platform-4-2-Final-Has-Been-Released
many of these issues occur because of the misconfiguration of LDAP addresses, ports etc... it's better to eliminite ABP and try to work on a simple LDAP console application. @maliming can you create a very simple console app with https://github.com/flamencist/ldap4net . so that we'll see if the problem is in the framework or in configuration.. you can share it on your GitHub account
tell me what's your Volo.Abp.Commercial.SuiteTemplates package version?
it's written in your *.Domain.Shared.csproj file.
so I guess you add the module as below
plus you need to verify your email address to get it working
