DNN调试利器DNNDebug.aspx--如何调试出错信息不具体的程序错误-优快云博客

本文介绍了一种用于调试DotNetNuke (DNN) 应用程序的方法，通过使用特定的调试页面来定位web控件加载时出现的问题。该方法帮助开发者快速找到错误源头。

有些时候DNN中程序出错的提示没有指出具体的出错位置，如果使用断点跟踪也不知在何处插入断点，这样我们debug完全只能靠猜测，比如如下的出错提示：

Error

Error: Edit Content is currently unavailable.

DotNetNuke.Services.Exceptions.ModuleLoadException:

External component has thrown an exception. ---> System.Web.HttpCompileException: External component has thrown an exception.

at System.Web.Compilation.AssemblyBuilder.Compile()

at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()

at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath)

at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)

at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)

at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath)

at System.Web.UI.TemplateControl.LoadControl(String virtualPath)

at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) in

E:\Development\DotNetNuke\InstallArea\DotNetNuke_04.08.03_Source\Library\Components\Skins\Skin.vb:line 492 --- End of inner exception stack trace ---

使用这个文件就可清楚的看到是哪里出了问题：