Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Load ExceptionModule Load Exception
Previous
 
Next
New Post
4/9/2008 7:07 PM
 

Thanks to everyone for trying to help out on this.  It turns out the problem was my local site was on version 4.8.1 and the remote site was on 4.8.0. 

For anyone having this problem I discovered this by creating a very simple "HelloWorld" module with nothing but a label on it then installing on the remote site.  This gave me a much more meaningful error.

 
New Post
4/9/2008 7:52 PM
 

Your @ Control directive and namespacing appears to be correct. Most often the CreateResourceBasedLiteralControl error is due to namespacing or other mismatch between the .ascx or .aspx and the codebehind. The reference in the error to 'ASP.desktopmodules_cersdb_cersdb_ascx' reminds me of the default class name that one gets when creating a usercontrol in VS2005 or VS2008 before editing the @ Control directive and the codebehind to use the desired namespace and class name. With a compiled module project, each control (.ascx file) will have an automatically generated designer file as well as the codebehind file. In your case the designer file should be named CERSDB.ascx.designer.vb. Usually, but not always, when one modifies the namespacing and class name in the .ascx and/or codebehind, that in the designer automatically changes to match. Check to see if you have a CERSDB.ascx.designer.vb file and that the namespace and classname exactly match those in the codebehind and if necessary make the change and then recompile.

EDIT: When I posted the above, your last post had not yet appeared. Glad you got it worked out. That's the first time I've seen the CreateResourceBasedLiteralControl error caused by a DNN version mismatch - usually the error for that is quite to the point.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
5/8/2008 11:50 AM
 

Hello Everyone,

I have a query....I developed the module on DNN 4.7.0 and when I installed the module on the server (DNN 4.8.2)....its installed properly but when I placed the module on the page I got the following error-----however its working fine in local......

DotNetNuke.Services.Exceptions.ModuleLoadException: D:\inetpub\supp\DesktopModules\CRE\DisplaySingleCategoryProduct.ascx(10): error BC30456: 'CreateResourceBasedLiteralControl' is not a member of 'ASP.desktopmodules_CRE_displaysinglecategoryproduct_ascx'. ---> System.Web.HttpParseException: D:\inetpub\supp\DesktopModules\CRE\DisplaySingleCategoryProduct.ascx(10): error BC30456: 'CreateResourceBasedLiteralControl' is not a member of 'ASP.desktopmodules_CRE_displaysinglecategoryproduct_ascx'. ---> System.Web.HttpCompileException: D:\inetpub\supp\DesktopModules\CRE\DisplaySingleCategoryProduct.ascx(10): error BC30456: 'CreateResourceBasedLiteralControl' is not a member of 'ASP.desktopmodules_CRE_displaysinglecategoryproduct_ascx'. 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.Compilation.BuildManager.GetVPathBuildResultWithAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.BaseTemplateParser.GetReferencedType(VirtualPath virtualPath, Boolean allowNoCompile) at System.Web.UI.BaseTemplateParser.GetUserControlType(VirtualPath virtualPath) at System.Web.UI.MainTagNameToTypeMapper.ProcessUserControlRegistration(UserControlRegisterEntry ucRegisterEntry) at System.Web.UI.BaseTemplateParser.ProcessDirective(String directiveName, IDictionary directive) at System.Web.UI.TemplateControlParser.ProcessDirective(String directiveName, IDictionary directive) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) --- 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) 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.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.GetVPathBuildResultWithAssert(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) --- End of inner exception stack trace ---

I didnt find any solution....Any help would be appreciated

Thanks and Regards

Sandeep

 

 
New Post
7/14/2008 6:56 AM
 

Hi,

I have similar type of problem!!

I had develope module using dnn 4.5 for server running dnn 4.8.2. Problem is when we add module on any page we get following error summary!!

"Unable to Cast Object of Type 'ASP.DesktopModules_ViewModule_Ascx'  to type 'DotNetNuke.Entities.Modules.PortalModuleBase' --> System.InvalidCastException: Unable to cast object of type 'ASP.DesktopModules_ViewModule_Ascx' ........


Any one having any idea. Please provide some infromation . How i can sort out this problem.
Thx.

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Load ExceptionModule Load Exception


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out