Activities of "EngincanV"

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.

[Bertrand] said:

[EngincanV] said:

[alper] said: ohh sorry, in your first message I just saw you tried the free version. @Engincan, why can we not get the source code of LeptonX PRO with that command?

Actually, we can get the source code of the LeptonX Theme Module with the command: abp get-source Volo.Abp.LeptonXTheme (.Pro was redundant at the end)

@Bertrand, please try with the command (abp get-source Volo.Abp.LeptonXTheme) and then the source-code will be downloaded:

Hi EngincanV Hi alper,

Thank you for your answers. But as I said in the original post, I already tried to download the Volo.Abp.LeptonXtheme module. This source code only have a few files that are not the ones I am looking for.

I need to modify the main sidemenu (left) and the settings side menu (right) and the mobile navbar and the modal menu that is opened by it. This package is not providing these components.

As @masum.ulu said in his post https://abp.io/support/questions/7811/Commercial-source-code-to-angular-package. We should be able to download 4 angular packages : "lepton-x", "lepton-x-abp-core", "lepton-x-core", "volo-lepton-x".

With this command we only have the "volo-lepton-x" one.

Yes, with the command abp get-source Volo.Abp.LeptonXTheme you only get volo-lepton-x. If you need other packages, you need to use the abp add-package command for packages, as you mentioned, and you don't need to pass the --old flag, because 4.2.2 is the latest stable one yet:

abp add-package @volo/abp.ng.lepton-x.core --with-source-code
abp add-package @volo/ngx-lepton-x.core --with-source-code
abp add-package @volosoft/abp.ng.theme.lepton-x --with-source-code

So, your first approach was right but it seems there is a problem in v4.2.2 for these packages, when I tried them, it gave the same error as you got. But, if you pass the version as an earlier version, such as v4.2.1, then it installs.

i

I've created an issue just before and we will fix the problem in v4.2.2. I'll let you know when it's fixed, but in the meantime, if it's important for you, then you may go with v4.2.1.

Regards.

[konstantinidis.f] said: Has there been any progress since those issues reported by the AI above? Or are we stuck with dealing with the warnings?

Hi, we made some enhancements on nullability on the generated codes before, especially on the app service and entity layers:

However, we might need to reevaluate this with all layers using a fully nullability-enabled solution. I'll create an issue for that.

[alper] said: ohh sorry, in your first message I just saw you tried the free version. @Engincan, why can we not get the source code of LeptonX PRO with that command?

Actually, we can get the source code of the LeptonX Theme Module with the command: abp get-source Volo.Abp.LeptonXTheme (.Pro was redundant at the end)

@Bertrand, please try with the command (abp get-source Volo.Abp.LeptonXTheme) and then the source-code will be downloaded:

Could you please confirm the version in which this fix will be included, and proceed with refunding the credit for this support ticket?

Hi @chrisalves, thank you for your kind words and for bringing this to our attention. I’ve created an issue for this and set its milestone to 9.3-final, which means we’ll aim to address it in the upcoming patch release.

I’ve also refunded your credit just now. Thanks again for reporting the problem.

Regards.

[chrisalves] said: Hi Support Team,

The A.I. answer above provided a reference to a similar situation but it is an 1 year more ticket on a older ABP version as below

Please provide an workaround to apply on my project as it is a BUG unfixed yet to help me move forward with this development.

Hi, please ignore the bot's response. I've identified the problem, and here is a quick workaround for you:

1. Open your Products.razor.cs file and update the file path:

- _jsObjectRef = await JsRuntime.InvokeAsync<IJSObjectReference>("import", "/Pages/Products.razor.js");
+ _jsObjectRef = await JsRuntime.InvokeAsync<IJSObjectReference>("import", "/js/file-cleanup.js");

2. Then, open your main application, create a /js/file-cleanup.js file under the wwwroot folder with the content:

export class FileCleanup
{
    static clearInputFiles()
    {
        var fileInputs = document.querySelectorAll("input[type='file'].file-input");
        for (var i = 0; i < fileInputs.length; i++)
        {
            fileInputs[i].value = null;
        }

    }
}

window.FileCleanup = FileCleanup;

Then, it should work as expected. I'll create an internal issue to fix this problem, but you can go with the current workaround.

Regards.