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.0Deploy DNN with VS.NET 2005 or Any Other Way?Deploy DNN with VS.NET 2005 or Any Other Way?
Previous
 
Next
New Post
1/29/2007 2:05 PM
 

Sorry if this is a repeat. I think I lost the first attempt of this post.

Working with DNN 4.3.5, VS.NET 2005, SQL Server 2005 Full Version

Tried using 'publish' feature in VS.NET to no avail. To my amazement, I cannot find any useful threads or posts on this topic. I must be missing something obvious. I simply want to move my working version of DNN from my local development machine to a live server. Please help, and if you must use terms like 'gac' please explain what that is or how to do it. Thanks in advance.... awaiting posts eagerly.

Frank

 
New Post
1/29/2007 2:16 PM
 
The easiest way is to XCopy the files to your live server (ie copy the files in your local folder to the remote folder).  You will need to modify the web.config with the connection string for the remote sites Database

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
1/29/2007 2:27 PM
 

Wow, thanks for the quick response. Does ftp result the same xcopy? I ask because I used ftp to uload the entire site, but I get an error that shows:

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

 

The thing is though, I do have it set to 'Off' as shown from my web.config below:

    <!-- set debugmode to false for running application -->
    <compilation debug="true" strict="false">
      <assemblies>...      </assemblies>
      <buildProviders>...      </buildProviders>
      <codeSubDirectories>  ...      </codeSubDirectories>
    </compilation>
    <!-- permits errors to be displayed for remote clients -->
    <customErrors mode="Off" />

 
New Post
1/29/2007 3:13 PM
 
If you have it set to off in your web config, I would check with your hosting provider to see if they can double check the setup of the virtual directory.  With my hosting provider they had incorrectly setup the virtual directory and no matter what I tried I was not able to view the error until they changed the settings.

-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
1/29/2007 3:17 PM
 
Yes, I think you are right. I am working on it now. Do you by chance know what the important setting on the virtual directory are and what they should be set to?
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Deploy DNN with VS.NET 2005 or Any Other Way?Deploy DNN with VS.NET 2005 or Any Other Way?


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