Activities of "alboy"

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

Are there any future plans to add support for the Volo.Forms module for Blazor? If so, is there a timeframe? It's kind of odd that this premium module is not supported in either Blazor WebAssembly, Blazor Server, or Angular. Was very upset to see that after spending ages debugging why it wasn't working, I stumbled upon a one-liner in your documentation to say it's not supported. I don't really want to have to spin up a separate site to host unsupported modules...

Maybe don't let users add the Forms module if it's not supported, or throw up a warning or something.

Okay, I understand now why the error has occurred, the explanation is much appreciated! I'll implement the workaround and deal with it for now.

Just for clarity, and in case you want insight into my reasoning behind why I did this, the reason it's ticked off is because of changes made in the templates I sent you. I wanted to add custom controls on the create/update modals. So I edited the templates to add custom code hooks in between each field, allowing me to customize the property fields on the modals etc. This way I can have lots of fancy interactive fields to create my entities, for example, for a name property on a given entity I might have an icon button to the right of the field to generate a random name, or a button to test a connection string etc.

Thanks again for your quick response

Hi, thanks for the response. I've responded with a zip of my .suite folder. I await your response!

ABP Suite seems to be failing to generate entities correctly. I can't find anyone else experiencing this problem looking at previous support tickets.

From what I can see, there is nothing mentioned in the logs even after setting suite logging verbosity to verbose. I am unsure of exact reproduction steps, but this has happened on 3 individual projects (I can share each json file if you want)

After a certain amount of entities created, it gets to a point where it generates malformed entities.

Here is an example of what is generated in MyEntity.extended.cs, with basic string properties "TestOne", "TestTwo", and "TestThree"

    public MyEntity(Guid id, )
        : base(id, )
    {
    }     

This is invalid code that of course will not compile. It seems to be failing to add properties of my entity in several places, like the base entity, extended entity, as well as create and update methods in the backend. It should look like

    public MyEntity(Guid id, string testOne, string testTwo, string testThree)
        : base(id, testOne, testTwo, testThree)
    {
    }     

I have tried versions 8.1.3 (where I first noticed the issue), 8.1.4, and 8.2.0-rc5. I've also tried changing generation options like turning off crud page generation, turning off custom code, disabling backend etc and it didn't seem to make a difference.