Products

Solutions

Resources

Partners

Community

Blog

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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why the main  DotNetNuke site is not  Web application project ?Why the main DotNetNuke site is not Web application project ?
Previous
 
Next
New Post
9/17/2008 2:57 PM
 

Hi All,

I just wonder why the DNN team decided to use website model when they start the  new dnn version 4 ?

I beleive the DNN website must be WAP ,because generally the website model used in the small websites and its really not good when you try to put it in the source control systam like Source safe .

Also , I recently noticed that the dnn install versions contains the code , and when i created a PreComplied version from the website ,the errors started to appear .

One of the errors happened after i tried to install the Dnn using the precomplied version .  in isntallation wizard and after entering the host passwrord , the intaller creates the App_Code folder and add some authentication providers classes to that folder ,which then throws a new error telling that you can't have App_Code when the website is PreComplied .

 

 


Anas Ghanem,
My blog
 
New Post
9/17/2008 4:27 PM
 

sorry, but precompilation is not supported.

WSP is used, because it is easier to make changes. I am not aware of problems in conjunction with source control.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/17/2008 5:04 PM
 

There is quite a history around this.

During the Spring and Summer of 2005 when we started to move to .NET 2.0 - there only was the socalled Website Project (WSP) so as we had decided to try and have a 4.0 version released to coincide with the release of ASP.NET 2.0 in Nvember 2005, that was our only choice.

Because of our complaints to MS (as well as the complaints of others), Web Application Projects were released during Spring 2006 as an "Add-on".

By this time we had made considerable investment in the WSP approach and it was decided to stick with it.

According to MS - there is no significant performance/scalable differences between the two.

We do not support precompilation for two major reasons:

  1. We use the App_GlobalResources and App_LocalResources folders for our xml based language files.
  2. As you discovered we support the use of App_Code for WSP based modules.

Both of these are incompatible with precompiled websites.


Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
New Post
9/17/2008 5:46 PM
 

Anas Ghanem wrote
 

I beleive the DNN website must be WAP ,because generally the website model used in the small websites

DotNetNuke.com is a very large website. As I write this there are 1300+ active users.

Anas Ghanem wrote

and its really not good when you try to put it in the source control systam like Source safe . 

It works fine with Source Control, please see:

Using Source Control with DotNetNuke



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
9/23/2008 2:31 PM
 

Charles Nurse wrote

During the Spring and Summer of 2005 when we started to move to .NET 2.0 - there only was the socalled Website Project (WSP) so as we had decided to try and have a 4.0 version released to coincide with the release of ASP.NET 2.0 in Nvember 2005, that was our only choice.

Thanks Charles , I think if the WAP was availabe at that time and if it was supported by VWD express editions , then i think it would be esier to migrate vs 2003 websites to WAP , and i think you may chose it instead of WSP.

Michael Washington : The website project is not playing good with visul source safe , because source safe was designed to work with project files , and believe me , the WAP is much better for source controls .

Also website project doesn't support files/folders execlude , and every time i want to execlude folders from source safe ( like core desktopmodules folders ) , i have to make those folders hidden using windows explorer so that they will not included in the website project.

 


Anas Ghanem,
My blog
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why the main  DotNetNuke site is not  Web application project ?Why the main DotNetNuke site is not Web application project ?


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