Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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.0WST vs. WAP, HTTP vs. File-based, under DNN vs. separate proj?WST vs. WAP, HTTP vs. File-based, under DNN vs. separate proj?
Previous
 
Next
New Post
12/5/2007 1:59 PM
 
Gennadiy Vanin (Геннадий Ванин)


Joined: 2/4/2007
Posts: 53

I am newbie in DNN4 module development and I'd like 

I'd like to better understand the implications (shortcomings and advantages) of developing the modules using
 VS2005:
 1) 
Web Application Projects (WAP) or CodeBehind model) vs. Web Site Projects (WST) or Code-Beside model

DNN4 is based on WST , where every as*x+.vb produces its own dll with arbitrary dll name.
Though deployment and versioning are obviously easier with WAP.

2)IIS-based vs. embedded in VS2005 webserver (File Based)
3)Inside DNN structure vs. separate project

What do you use for module development?
What are pros and contras?
 
New Post
12/5/2007 4:14 PM
 
Ian Robinson


enlivenhq.com
Joined: 1/6/2006
Posts: 921

For your development environment, I suggest:

  • extracting the source version of DNN (oldest version your modules need to support)
  • use IIS based web server (set up a virtual directory pointing to the website directory inside your source folder)
  • set up a new project/iis web site within your desktopmodules folder
  • use C#!
  • use WAP style
  • use NANT

This is a personal preference and what we generally do at Engage Software. Your business needs may dictate another configuration (as ours sometimes do).

take care,

Ian

Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
New Post
12/5/2007 9:20 PM
 
Gennadiy Vanin (Геннадий Ванин)


Joined: 2/4/2007
Posts: 53

Ian Robinson wrote

For your development environment, I suggest:

  • extracting the source version of DNN (oldest version your modules need to support)
  • use IIS based web server (set up a virtual directory pointing to the website directory inside your source folder)
  • set up a new project/iis web site within your desktopmodules folder
  • use C#!
  • use WAP style
  • use NANT

This is a personal preference and what we generally do at Engage Software. Your business needs may dictate another configuration (as ours sometimes do).

take care,

Ian


Hi, Ian,
this is informative to know this.
But I already knew most of these reviewing tutorials and searching on internet.

But I do not fully understand the reasons behind most of choices.

Especially I'd like to understand what is the reason of having source version of DNN?
Will it hinder and in which way the module or portal development?
Is not StarterKit version is more convenient and fast?

Why IIS and not file-based?
Again, file-based seems to be more fast and convenient
Especially because one of my PCs has screwed/unworking IIS but file-based projects/VS2005-internal webserver works fine
What advantages does give IIS and what are shortcomings of file-base?

Then what are your prefereances in the use of database and why?
Is it default file-based \App_Data\Database.mdf

I'd like to know the rationale behinf each choice

Guennadi Vanine --- Gennady Vanin -- Геннадий Ванин
 
New Post
12/6/2007 12:08 AM
 
Chris Hammond


Chris Hammond's Avatar

Chris Hammond's Avatar

Chris Hammond's Avatar

www.christoc.com
Joined: 1/14/2003
Posts: 7319

1. Source Version - Having the source version makes it easy to open up the DNN solution and step through code in debug, allowing you to track down any issues/code inside of DNN that you might find useful.

2. We (Engage) have had far better luck using Virtual Directories in IIS for development than dealing with the built in webserver for visual studio. You can also access the site without having to fire up that webserver assuming IIS is always running

3. SQLExpress, in my humble professional opinion just blows. You'll get far less hairloss (from pulling it out) if you just go with SQL 2k or 2k5 and skip SQLExpress all together. You should really take my word on this

 

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
12/6/2007 4:08 AM
 
AliCommerce

www.AliCommerce.com
Joined: 8/8/2007
Posts: 238

IMHO, If you develop a commercial module, choose WAP; If you develop a complex module for internal use, choose WAP; otherwise, WSP should be fine too.

Good luck,

Frank

Frank Wang
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0WST vs. WAP, HTTP vs. File-based, under DNN vs. separate proj?WST vs. WAP, HTTP vs. File-based, under DNN vs. separate proj?


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