Products

Solutions

Resources

Partners

Community

About

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

HomeHomeDevelopment and...Development and...Getting StartedGetting StartedVS 2008 Solution and Project Structure (WAP)VS 2008 Solution and Project Structure (WAP)
Previous
 
Next
New Post
1/15/2010 1:49 AM
 


I am trying to understand some best practices with regards to VS2008 and DotNetNuke development and the best method for setting up a complex multi-project solution in Visual Studio 2008 for just two developers.  I want to load up the DNN core into the solution so that I can learn form how things are being done.

In looking at the core DNN solution/project, I see that a separate VB project has been created named "Library". Could someone explain why this was broken out from the DNN web site project. Was this done because DNN decided to use a WSP project for the core instead of a WAP project (to support limited VS Express)?

If I am using VS2008 Standard and WAP projects are my preferred project type, is there any reason not to convert the DotNetNuke WSP, the Library project and Core Module Projects into WAP projects?   If someone has done this already I would love to hear how they set up their solution structure.

I came across the following inconsistencies in the core modules source projects:
Some of the core module projects appear to be built as VB Projects (Blog) and others are WAP projects (Events) .
Some of the code modules appear to have the SQLProvider file broken out into separate projects (creating lots of small projects) and some, including the templates, have it included as part of the module project.
Some of the module projects reference common dlls in the DNN Website bin and others reference the same dlls within the library project.
What is the recommended methodology (location) for referencing common DLLs. For example: Where should my new module reference the DotnetNuke.dll and Microsoft.ApplicationBlocks.dll?

Any recommendation are appreciated.

Les.

 
New Post
1/15/2010 4:13 AM
 

Library contains source code of DotNetNuke project, i.e. all classes which get compiled into dotnetnuke.dll, while web site is a WSP with all the UI


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting StartedVS 2008 Solution and Project Structure (WAP)VS 2008 Solution and Project Structure (WAP)


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