Activities of "EngincanV"

[vu.lang] said: Thanks. Do you have any plans to add support for DateTimeOffset in the near future?

There is no certain date or milestone for supporting the DateTimeOffset type. However, we have an issue for that in the backlog, and in each sprint, we prioritize some features according to your requests.

Hi, ABP Suite does not support DateTimeOffset for now. It supports DateTime, DateOnly, and TimeOnly types for date/time operations.

If ABP Suite does not support, are there any other ways to define the type as DateTimeOffset without manually changing the generated C# code?

Actually, there might be one tricky way to do that in the current structure: You can customize all DateTime templates and change the relevant places to DateTimeOffset type. But this approach might be programmatic, because in your solution then you'll not be able to use the DateTime type, and also schematics might not reflect the changes as expected. Btw, i don't suggest to customize templates for that, but it seems this is the only way for now, and it's really problematic.

Regards.

[rafael.gonzales] said: Not sure if it's related but I see this in the developer tools of the browser when running ABP Suite

Hi, it's not related to that, but this is also something we need to fix. I'll add to the bundle with 9.3.2.

For your main problem, I'll try to reproduce it today, and write back asap. If I'm not able to reproduce it, i may ask your need to send your project via email.

Regards.

Hi, as far as I understand, you said that when customizing an existing template (like Frontend.Mvc.Page.CreateModal.cshtml.txt, for example), it's not applying it correctly. So, to test it out, I've created a new layered MVC application and customized the related template, and the changes are there as expected:

Customized the template from the /Templates page (and simply added a div with a paragraph):

This customization should add a file into your .suite folder:

Here is the generated code:

Did I understand you correctly? Can you check that your template has a customized badge on the templates page or not?

[guven.uysall] said: Hi,

How can we upgrade from 6.0.2 to 9.2 as best practice? Should we follow the migration guide step by step, from 6 to 7, from 7 to 8, and finally from 8 to 9? Or should we just go from 6 to 9?

Hi, starting a step-by-step migration would be better to fix the problems easily. You can check the relevant migration guide after each upgrade: https://abp.io/docs/9.3/release-info/migration-guides/index

Hi @guven.uysall, the issue you're encountering is due to the fact that version v6.0.2 is no longer supported. The earliest available version is v6.0.3, which is why you're seeing this problem.

Please update both the ABP Suite and the ABP CLI to version v6.0.3, and install the corresponding template. This should resolve the issue.

Hi @ayse.elgoren, the issue you're encountering is due to the fact that version v6.0.2 is no longer supported. The earliest available version is v6.0.3, which is why you're seeing this problem.

Please update both the ABP Suite and the ABP CLI to version v6.0.3, and install the corresponding template. This should resolve the issue.

[48949912] said: Anyone else can help me to sovle this problem?

Hi, what's your problem exactly? ABP Suite generates CRUD pages for the Microservice Template. Actually, we even have a full Microservice Development Tutorial, which you can check at https://abp.io/docs/latest/tutorials/microservice?UI=NG&DB=EF

Also, you may need to follow the instructions here: https://github.com/abpframework/abp/issues/20827#issuecomment-2624232973

[alboy] said:

[AI-Bot] said: This error ("An internal error occurred during your request!" with a NullReferenceException in ABP Suite's CRUD Page Generator) is a known issue, especially in modular or microservice solutions, and is often related to the way ABP Suite parses your solution's structure and DbContext extension files.

How to Resolve

1. Check for Multiple *DbContextModelCreatingExtensions.cs Files

   • ABP Suite expects only one *DbContextModelCreatingExtensions.cs file per module. If you have more than one (e.g., both LeadsDbContextModelCreatingExtensions.cs and LeadsCustomDbContextModelCreatingExtensions.cs), Suite may fail with a NullReferenceException.
   • Solution: Keep only one such file per module and move all configuration methods into it.

2. Verify File Paths in Suite Configuration

   • Ensure that your solution's .abp/suite/appsettings.json points to the correct paths for your DbContext and extension files.
   • If you have moved or renamed files, update the paths or remove and re-add your solution in Suite.

3. Check for Missing or Misnamed Files

   • Make sure the expected files (like LeadsDbContextModelCreatingExtensions.cs) exist and are not excluded from the project.

4. Remove and Re-Add Solution in Suite

   • Sometimes Suite caches old paths. Remove your solution from Suite and add it again to refresh its internal cache.

5. Update to Latest Suite and ABP Version

   • Ensure both ABP Suite and your project packages are on the latest compatible versions.

6. If You Need Custom EF Core Configurations

   • Since Suite overwrites the extension file, you can temporarily move your customizations to a separate method or file, then re-apply them after code generation.

References and More Details

• ABP Suite CRUD Generator: startIndex must be non-negative
• Suite code generation fails on microservice modules
• ABP Suite CRUD Generator: startIndex must be non-negative (older thread)

These support threads contain detailed discussions and workarounds for similar issues.

---

If you follow these steps and ensure only one *DbContextModelCreatingExtensions.cs file exists per module, the error should be resolved. If you need to keep custom configurations, consider merging them into the single extension file or waiting for an official fix that supports custom/extended files.

---

This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

Just to respond to the bot

1. There is no DbContextModelCreatingExtensions-esque file, and I'm not sure there ever was... Upon searching for it I can see it's a staple of the standard solution templates. But it's not in my solution.
2. .abp/suite/appsettings.json seems to have all the correct paths after checking them, however I did notice that the version for this project is null?

3. Again, LeadsDbContextModelCreatingExtensions this file doesn't exist. But again, it seems like it never did.
4. I've removed and readded the solution to abp suite multiple times, made no difference
5. As said in my original post, upgrades, downgrades, and preview builds have all been tried

Hi, actually AbpVersion should not be null. ABP Suite builds your solution and determines the version normally, but it seems in your solution it could not do that. Can you please set the AbpVersion as 9.2.2 and try again to see if it works or not?

[Bertrand] said: Ok thanks. Could you provide me the changelog from 4.2.1 to 4.2.2 please ? Just to check if I will have troubles in using the 4.2.1 instead of 4.2.2.

Hi, quick update, we've fixed the problem in v4.2.2 just now, so you can get the source code on the latest version.