I have just upgraded (on my localhost machine) to Dotnetnuke 05.01.04 (3). All of the HTML modules have stopped working. My other custom and 3rd party modules are loading with no problem. Any ideas on what can be done to fix the HTML module?

DotNetNuke.Services.Exceptions.ModuleLoadException: Could not load type 'DotNetNuke.Modules.Html.HtmlModule'. ---> System.Web.HttpParseException: Could not load type 'DotNetNuke.Modules.Html.HtmlModule'. ---> System.Web.HttpParseException: Could not load type 'DotNetNuke.Modules.Html.HtmlModule'. ---> System.Web.HttpException: Could not load type 'DotNetNuke.Modules.Html.HtmlModule'. at System.Web.UI.TemplateParser.GetType(String typeName, Boolean ignoreCase, Boolean throwOnError) at System.Web.UI.TemplateParser.ProcessInheritsAttribute(String baseTypeName, String codeFileBaseTypeName, String src, Assembly assembly) at System.Web.UI.TemplateParser.PostProcessMainDirectiveAttributes(IDictionary parseData) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseReader(StreamReader reader, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.UI.TemplateParser.Parse(ICollection referencedAssemblies, VirtualPath virtualPath) at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() 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.Compilation.BuildManager.GetVPathBuildResult(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.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

 I came from version 05.01.02, and there were two script errors pointing to 5.1.3 and  5.1.4. Both mentioned a custom stored procedure that has nothing at all to do with the html module. The rest of the upgrade was successful.

.vb files are no longer needed for HTML module, it has been converted to WAP format using a dll.

if you have problems to run HTML on your site:

• delete content of folder /app_code/html/
• delete content of folder /desktopmodules/html/ (if present)
• delete file /bin/dotnetnuke.modules.html.dll (if present)
• delete file /bin/dotnetnuke.modules.html.sqldataprovider.dll (if present)
• unzip dnn_html_05.02.00.zip from /install/module in DNN 5.2.0 upgrade package
• in Host :: Extensions menu item, use command "extensions installation wizard" to re-install html module.

HTH