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...Custom Module outside of DNN ProjectCustom Module outside of DNN Project
Previous
 
Next
New Post
2/4/2009 8:16 AM
 

Hi

I'm new to DotNetNuke and I have my first question. I hope you can give me some hints ;)

We work on a project that uses DNN 4.x. Until now we developed our custom modules in the default folder "DesktopModules" of our web project. No doubt, this is an acceptable way for creating custom modules. But now we want to split our source code from the DNN in a own project (at least to an other location). I combed through the world wide web for some informations, but I didn't find a (good) solution. Now my question: is there established a way to develope custom modules we'd like to (perhaps in a class library?).

 
New Post
2/4/2009 1:46 PM
 

With proper project settings, you can place your source anywhere. You are right, there's nothing documented about this approach and I'll give you a brief overview to try it out:

  • Create a WAP project the usual way, inside desktop modules
  • Configure the project URL setting to point to the desktopmodules/mymodule/ path (project properties). Properly setting this value will allow you to debug normally later on.
  • Configure the application URL setting to point to the local development website (project properties).
  • Move the folder to where you want it to reside.
  • Fix the paths to the dll references
  • Fix the project URL setting

Of course, you will need to copy the necessary files to the local development site. It's better to automate this (either nAnt or some MSBuild tasks).

AFAIR, Philip Beadle has used this in the template for DNN and TDD that he posted in Codeplex, you will probably find that this is the approach being used there.


Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
New Post
2/5/2009 4:34 AM
 

With WAP it becomes difficult to do a copy-paste of the folder.

I think there are two solutions:
Make a Deploy configuration which can be selected and will build to a separate directory (like the old post-build event we had).

http://blog.theaccidentalgeek.com/post/2008/10/26/DNN-Tips-amp3b-Tricks-6-Building-Modules-in-VS-2008.aspx  

Or using NAND files for source and PA files:
http://www.engagesoftware.com/Blog/EntryId/74/DotNetNuke-Tip-Packaging-your-DotNetNuke-Module-using-NANT.aspx  

Third is deleting with a program or script the ascx files.

http://geekswithblogs.net/mnf/articles/87080.aspx

 

Does anybody has another (better) solution than the 3 above?

 
New Post
2/6/2009 8:10 AM
 

Thanks for your answers!

Indeed, your solutions are ok. But I'm not happy at all  I hoped, there is a proper way withou any "hacks". Has anybod tryed out following solution?

haacked.com/archive/2006/02/07/AddingWebUserControlToAClassLibraryInVS.NET2005.aspx

 

 
New Post
2/6/2009 10:27 AM
 

Store Integrator wrote
 

With WAP it becomes difficult to do a copy-paste of the folder.

Why? I don't have any problems doing it.


Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Custom Module outside of DNN ProjectCustom Module outside of DNN 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