Our blog contains the activity stream of Orchard Dojo: general news, new resources or tutorials are announced here.

Orchard Harvest 2026 program, Your website should integrate with your business systems - This week in Orchard (26/06/2026)

The full Orchard Harvest 2026 conference program is live, with the event taking place in Vancouver on September 10-11. Grab your early-bird ticket for just $280 and join the community for two days of sessions and networking!

Form submissions shouldn't end up in manual copy-paste routines. Orchard Core connects directly with Zapier, Make, and n8n to automatically trigger CRM updates, notifications, and more. DotNest's managed hosting makes the whole setup hassle-free!

The Health Checks module by Hisham Bin Ateya lets you restrict access by IP, apply rate limiting, and DoS protection for your health check endpoints, all configurable via JSON.

Managing multiple tenants on the same database just got easier. New RequireTablePrefix and TablePrefixPattern options, introduced by Mike Alhayek, let you enforce or auto-generate table prefixes (e.g., using the tenant name), so your setup is consistent and error-free out of the box.

No more guessing which properties to use for the Settings recipe step. Every module with configurable settings now includes a dedicated Recipe Configuration section with examples!

Ready to explore? Let's dive in!

Latest tutorials

Featured tags

AI
IIS
SMS
MCP
API
SEO
All tags >

How to debug a NuGet-based Orchard Core solution - Orchard Core Nuggets

How can you debug Orchard Core code when you’re working with a solution that loads Orchard packages from NuGet? Orchard’s packages are built with symbols so you can actually use them as source too! First, in Visual Studio be sure to uncheck “Enable Just My Code” under Tools → Options → Debugging → General. Then you can debug almost as usual: If you want to step into Orchard’s code from your own code then just put a breakpoint into your code as usual and hit Step Into (F11). It’ll open the Orchard source and debugging will work as usual. If you want to place a breakpoint anywhere in the Orchard Code that you can’t step into from yours (like a controller action) then do the following: Add a reference to the type anywhere in your own code. E.g. just write ItemController somewhere and import the namespace for OrchardCore.Contents.Controllers.ItemController. Hit Go To Definition (F12) on the type. Now you’re at the decompiled source of the type. This won’t be perfect but at least you’ll be able to place a breakpoint at the beginning of the method or other member you want to debug. Be sure to tick “Allow the source code to be different from the original” under the breakpoint’s settings. Run the app with the debugger attached. Your breakpoint will be hit and then the nice symbol sources will be used, just as when you step into Orchard’s code. Note that with “Enable Just My Code” you’ll also potentially see exceptions from the libraries you use or from .NET, even if they’re swallowed down the line. Depending on your work it might be better to keep the option ticked most of the time. Alternatively, you can also try opening a full Orchard source solution (with the Orchard version closest to what you’re using) and attach it to your own app. This sometimes works too but you can only debug Orchard’s own code in that case, not yours. Did you like this post? It's part of our Orchard Core Nuggets series where we answer common Orchard questions, be it about user-facing features or developer-level issues. Check out the other posts for more such bite-sized Orchard Core tips and let us know if you have another question!