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 with starter kitdeveloping with starter kit
Previous
 
Next
New Post
8/1/2007 10:27 AM
 

We're trying to set up a development environment, for creating a custom module. Down the road, we'll want to be able to develop others, so we want the solution to be extensible. We've succeeded in creating the environment, and beginning development, but there are some things that don't work the way we expected, so we're trying to figure out how to proceed.

First of all, we had problems getting debug to work. It seemed to be related to the use of a port (other than 80). We had to manually connect the debugger to the ASPNET process running on the non-standard port. That seems to be working ok now, but it was a bit of a stumbling block. Another stumbling block was the fact that the default cache time of 60 (in the .dnn manifest) kept the module from working correctly with multiview control, among others. Now that it is set to 0, that problem is resolved.

The biggest issue is, it appears that the DNN dynamic module template creates the new module within a single solution/project, and whenever we make a change and build, we are building the whole solution. In DNN3, we were used to a model (from Jan Blomquist, Traincert) where our custom development was a separate project, set to compile into the dotnetnuke bin folder, with appropriate DNN and ASP.NET imports and references, so when we made changes, we only had to build our own project. It was a little more manual, but it seemed a good approach.

We're also concerned about the process of building a private assembly when we're ready to package and distribute. Is there a clean way to do that with the starter kit approach of the module imbedded in a single solution? Or will we be better off if we have structured the environment so our development is in a separate project?

Another question - DAL code files in the module folder vs being placed in the App_Code folder. It seems that, in terms of protecting our intellectual property, it would be better if all the custom code for the module was in the module folder, rather than being spread across the solution. Is this optional using the starter kit (and the templates), or is the placement mandated?

I know this is a lot of questions in one post, but we would really appreciate some guidance here, so we can start on a solid path.

Thanks in advance for all help.

 
New Post
8/1/2007 6:59 PM
 

Starter Kit is targeted at development with the express editions (although it does work with VS 2005 bigger editions just fine).

The real issue here is not starterkit but the WSP method. You should use the WAP method if you want DNN 3 like development. Chek the Moving DNN 3 to DNN 4 WAP modules article here: http://nes.nesinteractivos.com/English/Articles/tabid/57/Default.aspx


Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0developing with starter kitdeveloping with starter kit


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