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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Trying to get basic new module to work in projectTrying to get basic new module to work in project
Previous
 
Next
New Post
3/31/2008 7:56 AM
 

So I hope it's okay to post this error message.  I got past all my other errors and now I have a simple module and when I try to access it , I get the following in the log and on my page.  I hvae reduced my page to only contain a bit of code to see if it shows up:

 

<%

@ Control Language="vb" codebehind="EditComments.ascx.vb" autoeventwireup="false" Inherits="Comments" %>

<

<

br /><br />div id="Comments" class="CommentsContainer">

 

<div style="padding: 3px;" class="head"></div>

testing 1 2 3

</

div>

and my code behind just has all the imports and

 

 

 

 

 

 

Public Class CommentsInherits DotNetNuke.Entities.Modules.PortalModuleBaseEnd Class

So I'm not sure what else to do.  Sooooo close, I think.

 

-------------------------------------------------------------------------------

 

ModuleId: 558
ModuleDefId: 129
FriendlyName: article comments
ModuleControlSource: DesktopModules/MetaComments/EditComments.ascx
AssemblyVersion: 04.04.00
PortalID: 0
PortalName: The Global Spiral
UserID: 1
UserName: host
ActiveTabID: 166
ActiveTabName: test4
RawURL: /website/test4/tabid/166/Default.aspx
AbsoluteURL: /website/Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 169a0c3d-aa03-472c-b803-da0ee46f667d
InnerException: Could not load type 'Comments'.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.TemplateParser.GetType
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Could not load type 'Comments'. ---> System.Web.HttpParseException: Could not load type 'Comments'. ---> System.Web.HttpParseException: Could not load type 'Comments'. ---> System.Web.HttpException: Could not load type 'Comments'.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.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.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 ---
Source:

 

 
New Post
3/31/2008 8:57 AM
 

Make sure that the Inherits attribute in the @Control directive of your module control's .ascx file specifies the COMPLETE namespace not jus the name of your code behind class. If you are using the compiled module (WAP) approach, check that the Root Namespace of your module project is either blank or if non-blank this root namespace will need to be pre-pended to the value of the Inherits attribute.

Also, in ASP.Net 2.0, your @Control directive should use the attribute CodeFile rather than CodeBehind and you would use Public Partial Class rather than Public Class in your .vb class definition.


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
3/31/2008 9:22 AM
 

Thank you!  The issue was the second part.  I made those changes and it works great.

 

Thanks again

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Trying to get basic new module to work in projectTrying to get basic new module to work in project


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