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
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Deploying a release version using web deployment project 2008Deploying a release version using web deployment project 2008
Previous
 
Next
New Post
9/12/2009 1:57 PM
 
Ahmed Mohamed

Joined: 4/1/2009
Posts: 2

 

Hi,
I am using a DNN source version, and the code is compiled successfully and runs well.
 
I am using “web deployment project 2008” to deploy the DNN web site to get a release version with no code inside (Just some dlls and aspx pages). Once I try to make a deployment version of the site to put it on the remote server, the solution built successfully, but when I try to use this release version, the login control disappears leaving an Icon (icon_authentication_32px.gif) instead.
 
This problem occurs on both the local and remote servers.
 
I am using version 5.1.2, and this is tested after a clean installation with no edits or page addition to the main site.
 
I am choosing the following deployment options in the web deployment project:
-      Release deployment.
-      Merge each individual folder to its own assembly.
 
I need your help, please.
 
Thanks in advance.
 
New Post
9/13/2009 1:36 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253

Sorry, DNN does not (yet) support pre-compilation of the site.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
9/13/2009 7:43 PM
 
Ahmed Mohamed

Joined: 4/1/2009
Posts: 2

Thanks sir for you reply,

But please let me make sure that i got what you said right.

Did you mean that, I cannot use the source code version to get a deployment version of DNN. And if I want to deploy a customized version of DNN, I should deploy the site with its source code?

Thanks in advance.
 
New Post
9/15/2009 8:59 AM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253

The following forum thread provides more information about the problems with precompiling a DNN site:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/78/threadid/27731/scope/posts/Default.aspx

As for customization of DNN, I strongly recommend that you do not modify the framework itself as you will face difficulties and much extra work each time the framework is upgraded. If, however, in the rare case that you find you must modify the framework, you would buiild a new dotnetnuke.dll from the DNN library project in the Visual Studio solution then either repackage the framwork for a remote installation/upgrade or simply copy the modified dotnetnuke.dll and any changed .ascx, etc. files to the website.

Customization should occur in modules and other extensions. Using the Website Application Project (WAP) approach to building modules allows you to compile the module code as a separate DLL to be packaged with the modules's user controls, resource files, etc. allowing deployment of the module without source code.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
 Page 1 of 1
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Deploying a release version using web deployment project 2008Deploying a release version using web deployment project 2008


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