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...Getting StartedGetting Startedcustom developmentcustom development
Previous
 
Next
New Post
1/30/2013 5:36 AM
 

If you are making modules that are to be used internally on your own sites - then you can bypass some of the complexities of compiled modules by building modules based on the WAP model.

Have a look at http://www.adefwebserver.com/dotnetnukehelp/ for a simple example of how to build WAP based modules.  They dont need to be compiled and they can be debugged inline.

 

 
New Post
1/30/2013 6:16 AM
 

Thank you very much
I will have a good look at this as it seems to be more of what I was trying to find.
We have a lot of custom plugins in our current CMS which would need to be migrated accross and I just need a clean way to migrate existing and build new modules on our own sites. I see there is also an advanced section that uses Ajax which is something we will use a lot in our modules

I will need to pacakage some modules for later use but for the moment I need a way to get us up and running asap.
Heres hoping Stuart

 
New Post
1/30/2013 7:37 AM
 
Chris - you're welcome. Glad you were able to make a v7 template.

Stuart - I'd start by choosing either v6 or v7 to be consistent and then develop your modules. Since there are differences between those versions of DNN and the module template, it may be easier.

In regard to your product not showing up once you add it, we need to know more about the module itself.

Developing modules can seem difficult at first and it does take a little time to get used to DNN but I assure you it can be done. Be patient, come to the forums and we'll see what we can do to assist.

Mark
 
New Post
1/30/2013 11:20 AM
 
Hi II followed your super simple module example and despite getting the Error  It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS. E:\dotnetnuke\Dotnetnuke\web.config 113 when I built the page. I could not find any extra web.configs???.
I was still able to to get the module into my DNN7 site following your advice. However, when I first added the module I could see all the account details laid  out in the gridview and the search tool worked fine while in the edit page mode.
As soon as I switched to layout mode just a blank page and module title, this happend with my previous attempt with a product module..Now it may be that I am not catching on to how these modules work but I assumed that the web user would be able to see and use it. must have configured something wrong?
Any pointers to both errors
 
New Post
1/31/2013 6:04 AM
 
Hi Guys
Just to say a big thank you for your help. I have now figured out why my modules did not display.. I had not gave the pages they sat on  the correct view permissions in the global page mangement (just at page level).
I only need to get my head around how skins are developed, deployed and used in DNN 7 and I will feel confident  enough to start our first project..
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting Startedcustom developmentcustom development


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