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.0Developing new ModulesDeveloping new Modules
Previous
 
Next
New Post
6/4/2008 9:13 PM
 

I'm new to DNN and have downloaded dnn.4.08.03 source and starter kit and have installed both.  I'm using Visual Studio 2005 and SQL Server 2005.  After reading alot of information in the doco and online, I'm trying to decide what is the best and quickest method for developing a new module.  The modules I want to create are a bit complicated and I've already developed as projects in asp.net.  Any tips or suggestions would be much appreciated.

Thanks!

 
New Post
6/5/2008 7:53 AM
 

Here's a thread that addresses two schools of thought on module development.  Other than deciding which method you will use, I would continue to digest the module developers guide authored by Michael Washington.  Also, loading the source code of the core dnn modules and looking through that code is a great way to learn.

Hope this helps and welcome to DNN
.

Paul

 
New Post
6/6/2008 1:58 AM
 

A lot really depends on where you want to take things.

But I would suggest you have a look at VS2008 and .net 3.5 as a long term goal for module development.
Its a pretty safe bet that much of future DNN support will be headed in that direction.

You may also want to have a look ath the discussions by michael washington regarding LINQtoSQL as well.
Ive been developing a new site based around that methodology and its really boosting development speeds
to no end - just not having to deal with DAL structure setups is a bit of a godsend on complex module sets.

As for workflows - if you modules are going to be inhouse - that is no need for closed compiled dlls.
Then I cant more than recommend the dynamic module approach - it makes for easy debugging and
no compile round tripping.

Westa

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Developing new ModulesDeveloping new Modules


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