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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.03rd party Module Source to Development3rd party Module Source to Development
Previous
 
Next
New Post
8/13/2007 12:52 PM
 

Goal:

Take a 3rd party module source, add it to my Dev DNN site, modify it, export the module in it's built format and add it to the real project. I have purchased a module and the source code was included. Now I want to be able to extend the module to do specific tasks. 

Problem:

I don't know how to take the original source and put it into dnn and make it something I can develope off of. I have not entirely figured out the DNN module structure but I have a bunch of user controls and .vb code and a Install directory and a Providers directory. I'm not sure where to put everything so that I can build the project and begin tweaking it.

It seems when the source is included for a module that it's not entirely in a format that you can do something with easily. Any help would be appreciated.

 


Sr. Software Engineer
 
New Post
8/13/2007 2:14 PM
 

It really depends on how the 3rd party module was developed. It might have been developed using VS2k5 with the WAP model, might have been developed using the standard website model, or might have been developed in VS2k3

In a perfect world you should be able to install a source package, just as you would an install package, through the module uploader, and then open the project in VS2k5. At least that is how we develop our modules that we sell on EngageModules.com.


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
8/13/2007 2:31 PM
 

The above statement is very true.  It all depends on the module and the development method used....

If you can tell us what module you are working with we might be able to tell you from experience.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
8/13/2007 2:37 PM
 

The module I"m currently working with is WildPortFolio

The original comment about if the source is available I should be able to install it. I"m not entirely sure I follow that method... WOuld I take the source and install (using dnn) as if it we a build release and when I open the project in Visual Studio 2005 be under "Desktop Modules" but in source format instead of a built version?

Is that statement correct if the sitaution was perfect? Or is that not how DNN modules work even in a perfect situation?


Sr. Software Engineer
 
New Post
8/13/2007 9:10 PM
 

I would really suggest - before you try to understand how someone elses module works.
Do some tutorials on building your own module - even a hello world type sample.

If you do this first - then you will have a better understanding of how the source files you purchased fit into the dnn module system.

Westa

 

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.03rd party Module Source to Development3rd party Module Source to 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