ABP Suite 10.5.0 Blazor #10810

7 Answer(s)

• 

  0

  AI-Bot created 2 months ago

  Support Team ABP Agent

  • This error means ABP Suite is running with a different template set than the one your solution outputs contain. In ABP, Suite reads its generation templates from the Volo.Abp.Commercial.SuiteTemplates assembly produced by your solution build, so ABP Suite version and Volo.Abp.Commercial.SuiteTemplates package version must match, and the solution must be built with a clean output.

  Fix (do in this exact order)

  1. Make sure ABP Suite is exactly the same version as your solution (10.5.0)

     • Update/downgrade ABP Suite so the installed Suite version is 10.5.0 (not 10.5.x vs 10.5.0 mismatch).
     • If you have multiple Suite versions installed, remove the others so you don’t accidentally launch a different version.

  2. Make sure your solution references Volo.Abp.Commercial.SuiteTemplates = 10.5.0

     • Check the version in your solution (often centrally managed via Directory.Packages.props / Directory.Build.props).
     • Ensure it is exactly 10.5.0 everywhere.

  3. Hard clean outputs (most common cause)

     • Close Visual Studio/Rider completely.
     • Delete all bin and obj folders under the entire solution (every project).
     • Reopen the solution and rebuild.

  4. Build the solution once after the clean

     • Build the full solution (or at least the main host project that Suite uses).
     • Then open ABP Suite and retry the generation.

  If you do (1)-(4), Suite will load the correct SuiteTemplates resources and the missing template error (e.g., ...Blazor.Page.Partials.Modal.Field.DateTime.NonNullable.txt) will disappear.

  • Reference (same root cause / fix: version mismatch + stale outputs): https://abp.io/support/questions/671

  ---

  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.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  cellero created 2 months ago

  I have used all ABP tools.

  1. Created new solution using ABP Studio V3.0.6
  2. Used ABP Studio | Tools | ABP CLI | Update ABP Packages to bring up to 10.5.0
  3. Ran that app to confirm all is running ok and it is
  4. Confirmed ABP Suite is running 10.5.0
  5. Created simple entity and got the error
  6. Remove the solution from ABP Suite and re added
  7. Repeated step 5 and go the same error

  Make sure ABP Suite version is equal to the Volo.Abp.Commercial.SuiteTemplates package version and that your solution has been built recently. The template below is missing: Volo.Abp.Commercial.SuiteTemplates.Templates.Frontend.Blazor.Page.Partials.Modal.Field.DateTime.NonNullable.txt

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  AI-Bot created 2 months ago

  Support Team ABP Agent

  • In your case the key detail is you created the solution with ABP Studio, then upgraded packages to 10.5.0. ABP Suite’s Blazor templates (the missing ...Blazor.Page.Partials.Modal.Field.DateTime.NonNullable.txt) are taken from the exact Volo.Abp.Commercial.SuiteTemplates version that your solution actually resolves and builds with. When you upgrade afterwards, it’s common that some projects still resolve an older Volo.Abp.Commercial.SuiteTemplates (or an older output DLL is still what Suite loads) even though the main app runs.

  Do this “hard verification + forced alignment” sequence

  1. Verify what version your solution really resolves for SuiteTemplates Run this in the solution folder (pick the main host project you run; typically *.HttpApi.Host.csproj or *.Web.csproj):

  dotnet list path\to\YourHostProject.csproj package --include-transitive | findstr /i "Volo.Abp.Commercial.SuiteTemplates"
  

  • If this prints anything other than 10.5.0, Suite will fail exactly like you see.
  • Fix it at the version-management root (usually Directory.Packages.props / central package management) so it is exactly 10.5.0.

  2. Clear NuGet caches (bin/obj clean is sometimes not enough)

  dotnet nuget locals all --clear
     dotnet restore
  

  3. Hard clean outputs again, then rebuild
     • Close IDE
     • Delete all bin and obj under the whole solution
     • Rebuild:

  dotnet build
  

  4. Make sure ABP Suite is not launching another installed copy

     • Ensure only one ABP Suite is installed and it is 10.5.0.
     • If you have multiple installations (common via Studio + standalone), uninstall the extras and keep only 10.5.0.

  5. Retry entity generation

     • Remove/re-add the solution in Suite (you did)
     • Generate again

  If steps (1)-(4) are correct, the missing template resource error disappears because Suite will load a Volo.Abp.Commercial.SuiteTemplates assembly that actually contains the 10.5.0 Blazor templates.

  Sources:

  • https://abp.io/support/questions/671

  ---

  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.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  cellero created 2 months ago

  nope. same: Make sure ABP Suite version is equal to the Volo.Abp.Commercial.SuiteTemplates package version and that your solution has been built recently. The template below is missing: Volo.Abp.Commercial.SuiteTemplates.Templates.Frontend.Blazor.Page.Partials.Modal.Field.DateTime.NonNullable.txt

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 2 months ago

  Support Team Fullstack Developer

  Hi,

  The missing-template error isn't about your NuGet package version. ABP Suite loads the Volo.Abp.Commercial.SuiteTemplates assembly once when it starts and keeps it in memory for the whole process. It doesn't reload it when you clean/rebuild or remove and re-add the solution. So if Suite loaded the templates before your upgrade (when your output still had the older assembly), it keeps using that old one no matter how many times you clean and rebuild. That's why all the steps you tried didn't change anything.

  The one step missing is fully restarting Suite:

  1. Build your solution once so the output is on 10.5.0.
  2. Close all ABP Suite processes completely (also close ABP Studio if you launched Suite from it, so no Suite process stays alive in the background).
  3. Reopen Suite and generate the entity again.

  If you want to confirm which assembly Suite actually had loaded, check the copy it runs from right after the error (it's the real loaded file, not the one in bin):

  $dll = Join-Path ([System.IO.Path]::GetTempPath()) "Suite.dll"
  [System.Diagnostics.FileVersionInfo]::GetVersionInfo($dll).FileVersion
  

  If that shows anything below 10.5.0, it's the stale copy, and a full Suite restart clears it.

  We'll also make Suite reload the templates when you re-add a solution so a full restart isn't needed for this in a future release.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  cellero created 2 months ago

  Ok thank you. That has worked.
  Suite is now generating entities without error.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 2 months ago

  Support Team Fullstack Developer

  Great 👍

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel