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.0Add Module but Getting ErrorsAdd Module but Getting Errors
Previous
 
Next
New Post
7/21/2009 2:08 PM
 

I created a relatively simple module using the DotNetNuke Compiled Module Project template with Visual Studio 2008.  The module works fine on my dev machine which is running DNN 4.8.4.

I have installed the module on my production server which is running 4.8.2.  When I put the module on the page, I get the following error:

Error: formSelector is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: C:\DotNetNuke\DesktopModules\formSelector\ViewformSelector.ascx(18): error BC30456: 'CreateResourceBasedLiteralControl' is not a member of 'ASP.desktopmodules_formselector_viewformselector_ascx'. ---> System.Web.HttpCompileException: C:\DotNetNuke\DesktopModules\formSelector\ViewformSelector.ascx(18): error BC30456: 'CreateResourceBasedLiteralControl' is not a member of 'ASP.desktopmodules_formselector_viewformselector_ascx'. 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.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

I am across some other postings with a similar error, so I checked my Specific Version setting and it is already set to FALSE for the DotNetNuke.dll.  Does anybody know what else I should look at.

Thanks

 
New Post
7/21/2009 2:30 PM
 

It looks like you might have an issue with the .ascx and .dll files being out of sync.

I would ensure that all files updated and deployed.  The site is having an isssue finding a method that it expects to exist.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
7/21/2009 9:04 PM
 

If your module has been compiled against dotnetnuke.dll v 4.8.4 on your development machine, you CANNOT install it into a DNN instance (such as 4.8.2) having an earlier version number. I recall having done just that once accidentally and received the same CreateResourceBasedLiteralControl exception. If you do want to target DNN 4.8.2 with your module, you will need to reference dotnetnuke.dll v 4.8.2 in your project and be sure that the require specific version setting is False to allow installation of the module in LATER versions of DNN.


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
7/22/2009 10:28 PM
 

Thanks, that did the trick. 

I downloaded th 4.8.2 version of the DotNetNuke.dll from my production server and compiled my module against that.  Then I uploaded my recompiled .dll and my module worked fine in production.

I can't thank you enough.

Dave

 

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Add Module but Getting ErrorsAdd Module but Getting Errors


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