Activities of "EngincanV"

[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.

[connect] said: No it doesn't help. I tried to run some small script as follows but still i getting the same error. I dropped my collections in local mongodb then it worked. How can i fix this to my production now?

 
public static class MongoDBGUIDMigrations 
{ 
    public static async Task Migrate() 
    { 
       BsonSerializer.RegisterSerializer(new GuidSerializer(GuidRepresentation.Standard)); 
 
        var connectionString = "mongodb://localhost:27017"; // Replace as needed 
        var dbName = "your-database-name"; // Replace with your DB name 
 
        var settings = MongoClientSettings.FromConnectionString(connectionString); 
        var client = new MongoClient(settings); 
        var database = client.GetDatabase(dbName); 
 
        // STEP 3: Get all collection names 
        var collections = await database.ListCollectionNamesAsync(); 
        var collectionNames = await collections.ToListAsync(); 
 
        Console.WriteLine($"Found {collectionNames.Count} collections."); 
 
        foreach (var collectionName in collectionNames) 
        { 
            Console.WriteLine($"\n🔄 Processing collection: {collectionName}"); 
 
            // Use BsonDocument to handle dynamic schemas 
            var collection = database.GetCollection<BsonDocument>(collectionName); 
 
            var documents = await collection.Find(FilterDefinition<BsonDocument>.Empty).ToListAsync(); 
 
            int updatedCount = 0; 
 
            foreach (var doc in documents) 
            { 
                var id = doc.GetValue("_id", null); 
 
                if (id == null) 
                { 
                    Console.WriteLine("Skipping document without _id"); 
                    continue; 
                } 
 
                // Replacing with same document will reserialize with Standard Guid format 
                var filter = Builders<BsonDocument>.Filter.Eq("_id", id); 
                await collection.ReplaceOneAsync(filter, doc); 
                updatedCount++; 
            } 
 
            Console.WriteLine($"✅ Updated {updatedCount} documents in collection: {collectionName}"); 
        } 
 
        Console.WriteLine("Migration complete. All documents now use UuidStandard format for Guids."); 
    } 
} 

Hi, to fix this problem, you should say to the driver to use the old format. There is a really good community article that exactly explains how to do that, which you can check at https://abp.io/community/articles/solving-mongodb-guid-issues-after-an-abp-framework-upgrade-tv8waw1n.

Can you check the article and apply the suggested solution? It should fix your problem.

[IgorG] said:

[EngincanV] said:

[IgorG] said:

[EngincanV] said:

[IgorG] said:

for some reason i get an error
Volo.Abp.Studio.AbpStudioException: Exception of type
'Volo.Abp.Studio.AbpStudioException' was thrown.

i logged in using command: abp login

What is your license type? (It should be Business or Enterprise to be able to get the source code of the module.)

i have a Team license. In this case how can i get markup of the UserManagement.razor page ?

Okay, no problem. I’ve shared the related file with you via email — please check your inbox and let me know if you need any further assistance.

Thank you. I see the layout. Can you also send me a code behind file ?

Sure, sent it over via email.

[david1] said: I don't believe the CRUD page generator is actually generating any code successfully because it is crashing before completing even step 1 (out of 10 steps). Is there somehow I can check what is causing the validation to fail that I can check and resolve?

After the error occurs during the first step, does the code generation still continue and show you an information dialog?

In my case, it threw a similar error but still completed the code generation and displayed an information dialog indicating success. I reviewed the generated code, and everything looked correct — I was even able to run the application and test it without issues.

I found that the root cause was a project I had moved on my machine, which was still pointing to its old location in the Suite's appsettings.json file (this file keeps a list of all solutions added to Suite). Once I corrected the path in that file, the problem was resolved.

Could you check if the same applies in your case?

[IgorG] said:

[EngincanV] said:

[IgorG] said:

for some reason i get an error
Volo.Abp.Studio.AbpStudioException: Exception of type
'Volo.Abp.Studio.AbpStudioException' was thrown.

i logged in using command: abp login

What is your license type? (It should be Business or Enterprise to be able to get the source code of the module.)

i have a Team license. In this case how can i get markup of the UserManagement.razor page ?

Okay, no problem. I’ve shared the related file with you via email — please check your inbox and let me know if you need any further assistance.