Activities of "EngincanV"

[rogercprops] said: My mistake. (Copy/Paste error)

I was able to install and upgrade to the latest version.

Thank you for working through this with me.

Thanks for your kind words. Closing the question...

Best regards.

dotnet tool install -g Volo.Abp.Suite --add-source https://nuget.abp.io/***/index.json

Hi, this is not correct; this is the reason why you get this problem. It should be: dotnet tool install -g Volo.Abp.Suite --add-source https://nuget.abp.io/<your-private-key>/v3/index.json (/v3/index.json is missing in your case)

Hi again, thank you for sharing the project and all the detailed information. I've reproduced the problem, and it seems there is a wrong dbcontext logic in ABP Suite.

You have two classes: CoreCustomDbContextModelCreatingExtensions and CoreDbContextModelCreatingExtensions, and ABP Suite is currently unable to understand the difference. So, for a quick workaround, you can delete the CoreDbContextModelCreatingExtensions and move the ConfigureCore method to the other file.

Then, when you generate it, it should generate successfully:

I'll create an issue for this and we will fix it asap, but for now, you can go with a single *DbContextModelCreatingExtesions class.

Regards.

[rogercprops] said: Why was this closed? I still don't have a resolution.

Hi, sorry for the inconvenience. It's probably closed by our support bot. I've checked the abp-suite NuGet package for the related version and we made some enhancements on our server. So, can you please try again and let me know if you are able to download ABP Suite or not?

[david1] said: Thanks, I've sent an email and description to that support email now.

Thanks, I got your project. I'll write you back in an hour.

[david1] said: I also sent sumeyye.kurtulus in one of my other tickets an email with a link to my complete project as-is. I can send you this project as well to see if you can reproduce that error on your end? If that's helpful please let me know your email so that I can send it to you privately.

Actually, this can be better to reproduce the problem. Please send the project to support@abp.io with the ticket number, and I'll look into it and write you back asap.

so perhaps it's related to a config of the "older" DDD modules we have in our project that is somehow different to the newer specification for 9.2.0+ ?

Hi, yes, actually I suspect this. I'll try it with your config and let you know about the status of the issue.

[rogercprops] said: Yes. rogerhopkins@Rs-MBP-3 ~ % abp login-info [07:06:12 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli 📌 ABP CLI 1.0.1 [07:06:14 INF]
Login info: Name: Roger Surname: Hopkins Username: rogercprops Email Address: roger@cprops.com Organization: Cooperative Processing Resources

Hi, thanks for the confirmation. The error message "Entry point file 'Volo.Abp.Suite.dll' for command 'abp-suite' was not found in the package" indicates that the NuGet package is either corrupted or incomplete. To fix this, you can clear your NuGet caches with the following command:

dotnet nuget locals all --clear

After this, please try again to install ABP Suite, and let me know if it works or not. Because it seems probably there is a suite package in your cache and it's corrupted somehow. (Sometimes it happens for global tools.)

[david1] said: Just tested it on older 0.9.25 versions and same issue. Also tested on a separate machine. Leads me to believe there's some kind of config file being read in our project that it doesn't like in the backend generation step (unchecking the backend generation step allows the latter steps to continue). Any way I can isolate what file it's encountering that it doesn't like?

I presume it's somewhere in the code in these sections of the Volo ABP Suite although I don't have access to the source code to diagnose it (Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync):

   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.CBf4WQwZkH(Boolean  , String  , String  ) 
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.gb34LXPXOW(Boolean  ) 
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.uuX4U4GI2l() 
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.ExecuteAsync(CrudPageCommandOptions options) 
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.CommandManager.ExecuteAllAsync(CrudPageCommandOptions options) 
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.CrudPageGenerator.GenerateAsync(EntityModel entity, Solution solution, EntityModel masterEntity, List`1 navigationConnections) 
   at Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync(Guid solutionId, EntityModel entity) 
   at lambda_method2077(Closure, Object) 

Please, share your entity metadata (under .suite folder of your solution) and solution information (appsettings.json file under the .abp/suite folder).

[consultant.ahmet.ulusoy] said: User click the today button and created the record. Creation Time saved as UTC , but Test Date Time saved as UTC+3

Hi, are you using IClock when setting the TestDateTime? If so, setting the kind to UTC should also apply to that property.

However, if you're using something like DateTime.Now, it uses the system's local time and ignores the Kind setting — which is exactly why we provide the IClock service. It centralizes time-related operations and ensures consistency across the application.

So, we recommend using the IClock service whenever possible to take full advantage of its benefits.