What is the best way to debug the Dynamic Module Loader?

Topics: Customizing Orchard, General, Troubleshooting, Writing modules
Oct 31, 2012 at 4:12 PM

We have a custom module that when imported via the dashboard, appears to import and Enable with no issues.  However, the module build does not get copied to the App_Data\Dependencies folder.  I am trying to determine why this is failing.  I suspect there is some issue with our module that Orchard doesn't like.

1) What log files are available to me to see what Orchard is doing in the background?  I am aware of Dependencies.xml, but that isn't showing anything really useful at this point.

2) For any log files that are available, do they have to be enabled in some way (I assume they do), and where are the log files placed?

3) I am trying to trace the code to find the 'msbuild' step where the code gets compiled, but I am not able to determine where this is actually occurring for a module loaded dynamically.  Where does this actually happen?



Oct 31, 2012 at 6:04 PM

Compilation errors should appear in app_data\logs like any exception.