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.0how do you guys develop with DNN?how do you guys develop with DNN?
Previous
 
Next
New Post
6/14/2007 2:12 PM
 

Gnot, usually a DNN module has its own contained environment: its own tables, its own settings, its own sprocs, its own logic. Good module design should include upgrade scripts for all sql needed to create or alter tables and sprocs for your module

 


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
6/14/2007 2:16 PM
 

gnot,

What I do is that I ensure that my development environment has all of the same skins and modules and I recreate some of the pages, but overall I make sure that I at least have the same modules and skins installed.


-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
6/14/2007 11:26 PM
 

I am probably go a bit overboard but I actually have 4 environments I use. The first 3 are located locally: Development which is used purely for code development and initial validation. Integration, this is where I test my install/upgrade/Uninstall procs. The 3rd local environment is a "prod" like environment that I copy locally from my production environment prior to testing. This is where I cunduct end to end testing of the module/code changes including validation that the changes I made have caused no problems elsewhere within the installation. I also do performance tuning at this stage (more db related) because in my experience you need to baseline/optimize performance against real world data.

This is probably more than is required for many sites but is also less than larger sites should go through.

Chris

 
New Post
6/15/2007 7:46 AM
 

When I develop a module each module gets it's own DotNetNuke installation. This makes it move fast because I use the WSP format (that works with Visual Web Developer Express).

I use SQL Server express for these installs so it only takes 2-4 minutes to set each one up. I usually use IIS because it is faster to view the page and debug.

I also use Visual Studio because it has the "Debug/Attach to process" that makes debugging very fast (a single feature like that is worth the $200 to upgrade from Visual Web Developer Express to Visual Studio).

I then create the .sql upgrade scripts like I would for any Core DotNetNuke module (I actually don't create uninstall scripts because I'm usually building modules for companies that would have a huge problem if some admin accidentally uninstalled the module and erased valuable company data :)

In my case the customers expect the module to behave like Core module (except the uninstall). Most importantly they expect it to upgrade like a normal DotNetNuke Core module. They already have live data so you must use .sql upgrade scripts, you can't just copy the database.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0how do you guys develop with DNN?how do you guys develop with DNN?


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