Hi, this file is being created/updated automatically by the dotnet-ef CLI whenever a new migration is added.
The problem that you are facing with this file is not related to ABP & ABP Suite because we are not making any changes to this file, we are just running the related dotnet-ef command (dotnet ef add migrations <migration-name>
) under the hood to create a new migration.
Hi @SuperBeastX3, I will check and write back to you asap.
There is an issue with the version 7.4 rc-3. I have an issue with the following packages that couldn't be restored with this version
Unable to find package Volo.CmsKit.Pro.Common.Web. No packages exist with this id in source(s): ABP Commercial NuGet Source, C:\Program Files\dotnet\library-packs, C:\Program Files\dotnet\sdk\7.0.307\Sdks\Microsoft.NET.Sdk.Web\library-packs, Microsoft Visual Studio Offline Packages, nuget.org
We have published the missing packages, please try again. (You might want to clear your Nuget cache if the package cannot be found on your first try.)
There is an issue with the version 7.4 rc-3. I have an issue with the following packages that couldn't be restored with this version
Unable to find package Volo.CmsKit.Pro.Common.Web. No packages exist with this id in source(s): ABP Commercial NuGet Source, C:\Program Files\dotnet\library-packs, C:\Program Files\dotnet\sdk\7.0.307\Sdks\Microsoft.NET.Sdk.Web\library-packs, Microsoft Visual Studio Offline Packages, nuget.org
Hi, thanks for reporting. We will fix the problem and publish the packages asap.
Further investigation of the ToDynamicListAsync method shows the new module uses
System.Linq.Dynamic.Core v 1.2.18
as opposed to the latest 1.3.4.Upgrading the package fixed the issue.
This was a new module created by the latest version of ABP Suite. V1.2.18 is marked as Vulnerable. This may need to be fixed in the Project Templates.
Thanks for reporting. We have already upgraded the package version to v1.3.3 in 7.4.0-rc.1:
I agree, 6 months is good, but as it is coded currently it is a session time, NOT 6months.
Okay, I will update the related part and it will be available in the next release.
Hi, as far as I know, some regulations by countries have limits like min 6 months of expiration (for example: Ireland).
Also, if we set the expire as Session then it will act differently in every browser. For example, in Safari, it will show the consent even if you switch apps, or in Internet Explorer, it's not taken into account at all. Thus, I think it's more suitable to add an absolute 6 months as the date for expiration.