Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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...Using Modules a...Using Modules a...How to deploy a DNNv4 (WSP?) ModuleHow to deploy a DNNv4 (WSP?) Module
Previous
 
Next
New Post
11/26/2010 12:26 AM
 
Jan Montano


www.kokoness.com.au
Joined: 10/25/2010
Posts: 84
Thank you for the reply William. I appreciate it a lot.

To answer your questions.

A. WSP
1. !Check. It does have an assembly in the site's /bin
2. Check. It has code files under a subfoler in /DesktopModules
3. !Check. It doesn't have the CodeFile Attribute

B. WAP
1. Check. It does have an assembly in the site's /bin
2. !Check. It has code files under a subfoler in /DesktopModules
3.Check. It does have the CodeBehind Attribute

It does look like that it's a WAP (though is has a source code deployed). Thanks for that clarification.

Earlier, I've replaced the old module's dll on the site's /bin with the new one. Also replaced the module's subfolder in the /DesktopModules. But it didn't work.

It works on my dev environment, I don't know why it's not on staging...

Error: Customised weed sheets is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The type initializer for 'Digicon_Woody_Weed_sheets.WoodeWeedsSheet' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Digicon_Woody_Weed_sheets.WoodeWeedsSheet' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Digicon_Woody_Weed_sheets.WeedSheetDataContext..ctor() at Digicon_Woody_Weed_sheets.WoodeWeedsSheet..cctor() --- End of inner exception stack trace --- at Digicon_Woody_Weed_sheets.WoodeWeedsSheet..ctor() at ASP.desktopmodules_digicon_woody_weed_sheets_woodeweedssheet_ascx..ctor() at __ASP.FastObjectFactory_app_web_fivd9ibd.Create_ASP_desktopmodules_digicon_woody_weed_sheets_woodeweedssheet_ascx() at System.Web.Compilation.BuildResultCompiledType.CreateInstance() at System.Web.UI.TemplateControl.LoadControl(IWebObjectFactory objectFactory, VirtualPath virtualPath, Type t, Object[] parameters) 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 ---
 
New Post
11/26/2010 9:10 AM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
Back when ASP.Net 2.0 and DotNetNuke 4.00.xx was first released, Visual Studio 2005 could not create a website application project only a dynamically compiled website project (WSP). Some developers started creating pre-compiled WSP hybrids which did produce a dll assembly and as I recall modified the projects .ascx files to reference the assembly which was given an odd name having what appeared to be seemingly random characters in its name.

Most likely, the module's business controller class registered in the module definition still referrs to the old namespace and class. Go to Host --> Extensions, assuming the site is on DNN 5.x or to Host --> Module Definitions if still on DNN 4.x to check and modify if necessary. It is also possible that the .ascx files also reference the now incorrect namespace.

As a final thought, are you re-compiling the module referencing the DotNetNuke assembly (DotNetNuke.dll) of the same or earlier version than that of the staging/production site. For example, if the project is built against DotNetNuke v 5.05.01 but the project assembly is then moved to a DotNetNuke 05.04.04 site, that will not work.

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
11/28/2010 6:57 PM
 
Jan Montano


www.kokoness.com.au
Joined: 10/25/2010
Posts: 84
Sorry for the ignorance but what would I check/modify with my module?
http://www.kokoness.com/work/WoodyWeedModuleDefinition.png

The DotNetNuke.dll file/product version is 4.9.4.17.
The DotNetNuke version on the staging site  is 04.09.04.
I'm assuming this is the same version.
 
New Post
11/28/2010 11:03 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
Jan,

From the image you posted, it appears that there is no business controller class. Since the module does not support the Upgradable, Portable or Searchable interfaces, it is not necessary to create and register a business controller class.

In looking over the stack trace you posted earlier, it appears that the initialization error is occuring when the class WoodeWeedsSheet is attempting to be created as the view control WoodeWeedsSheet.ascx is being loaded. Without looking at the structure, namespaces, etc. of your module project, I'm not able to come up with other suggestions. If you could post a screen capture of the VS 2010 project's property pages Application tab showing the assembly name and root namespace fields plus the first few lines of  WoodeWeedsSheet.ascx (showing @Control drective) and of WoodeWeedsSheet.ascx.vb  (showing namespace and class statements), I may be able to help. Also, the same for the WoodeWeedsSheet.ascx.designer.vb file if present?

Regarding the DotNetNuke.dll versioning question - all looks fine there.
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
11/29/2010 2:23 AM
 
Jan Montano


www.kokoness.com.au
Joined: 10/25/2010
Posts: 84
Here you go, you could check the files here.
 
 Page 2 of 3
Previous123Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...How to deploy a DNNv4 (WSP?) ModuleHow to deploy a DNNv4 (WSP?) Module


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