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

HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Module not generating  dll´s after compilation. Any ideas why?Module not generating dll´s after compilation. Any ideas why?
Previous
 
Next
New Post
9/15/2009 9:57 AM
 

Hi all, im having a bit of a problem developing a simple master detail module. Im using DNN 05.01.00 (773), and i have developed modules for previos version of DNN (a while ago, using the starter kits for VS), the thing is that, for now, AFAIK there´s no starter kit for this version of dnn. Here´s a list of the steps i´ve followed to develop the module:

-Created the folder App_Code/mymodule.

-Created the folder DesktopModules/mymodule

-Opened my dnn site with VS 2008

-Added a entry for the folder on codeSubDirectories of the web config.

-Created the info and controller class on the folder App_Code/mymodule.

-Created the ascx control with the grid on it on the folder DesktopModules/mymodule.

-Compiled the website on the vs (no exceptions)

-Added the module through the wizard of the dnn, adding also the definition, and the controls for it (selecting the codepage for the control and view for type).

 

The thing is that, every time i add the module to a page, nothing happends, and no DesktopModules/mymodule.dll is being created on the bin directory.

 

Can anyone point me on the right direction?

 

Tnks a lot for your time.

 
New Post
9/15/2009 7:50 PM
 

The steps you outline would create a module using the dynamically compiled website project (WSP) approach in which no module DLL will be created. When packaging the module, all source code files including those in App_Code/mymodule folder will be included in the package. If you want to create a module DLL and not include source code in a module package you should follow the compiled module,  website application project (WAP) approach.

There are several pinned posts at the top of this forum (or the corresponding Extend It! forum for DNN 4.x and VS 2005). You may also want to check Jon Henning's blog for obtaining the CodeEndeavors compiled module templates for DNN 5.x.

As far as nothing happening when your module is added to a page, there could be several reasons for that - one of the most common is assigning a non-blank ControlKey to the default view control of the module. If that control's ControlKey is non-blank, no module will be displayed and no error shown or logged.


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
9/16/2009 9:32 AM
 

Tnks a lot for the response William, it has definitelly pointed me on the right way; and the "leave blank ControlKey" worked like a charm!!!.

 

Tnks a millon for your help.

 

Good luck

 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Module not generating  dll´s after compilation. Any ideas why?Module not generating dll´s after compilation. Any ideas why?


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