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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install to remote serverInstall to remote server
Previous
 
Next
New Post
12/6/2006 11:50 PM
 

I have a server running in downtown Columbus which has my DNS, Email, Sql server and WebServer. I have my desktoop development system at home with Visual Studio on it. I configured a DNN database on my downtown server but downloaded the dotnetnuke to my development system. I installed the dotnetnuke template in Visual Studio then created a project based on that template. I built the web and then wanted to publish it to my downtown server. ( I have a free IP address without a domaain for testing ) so I tried to publish the DNN at that IP address. It took HOURS to do and when it was done only downloaded 17kb of files. The files were mostly the directory structure without data.

I set up my virtual directory with FULL CONTROL access to ASPNET. I'm running Framework 2.0 on the server.

What I'm not clear on is whether I can create the web with Visual studio on my development system then publish it on my remote server downtown. This is my first attempt at using dotnetnuke so I am a little confused. I don't want to have to put the visual studio on my server downtown since I can only access it remotely.

Thanks for any help.

Bob

 
New Post
12/7/2006 5:29 AM
 
dnn can be installed using "xcopy installation", so you just have to download the dnn install package, unzip it in the correct directory of your server (the root of your site), make the proper changes to web.config, and browse to your site... its as easy as that....

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
12/7/2006 9:18 PM
 

I want to create some of my own modules (at least I think I do) so I expect that I will need to build them with Visual Studio. When I have tested the module then I will want to put it on my server. Maybe I'm missing something. In the past, all websites that I've created using Visual Studio 2005 were done in such a way that I could develop and debug on my desktop system here at home and once completed then I could publish the site to my server. That's what I'd like to be able to do with dotnetnuke. Is that not something that is doable? I assume that just using the xcopy method will get my a very generic install without the ability to add or modify modules. Maybe that's something I won't need to do but I'd at least like to check it out.

Thanks,

Bob

 
New Post
12/8/2006 6:29 PM
 

I am replying to my own post. I discovered that if I set my front page author access to allow loading of executable files. After doing this the web was uploaded. Then I went to the site and it complained that I didn't have access on certain directories and prompted me to set access for NT AUTHORITY\NETWORKSERVICE to read, write and modify which I did. Then when I went to the site again, it completed most of the installation. There were some errors trying to install some of the modules.

When I clicked on the link that said click here to access your portal I got an exception. Here is what it was:

[HttpException (0x80004005): The directory '/App_Code/Reports/' is not allowed because the application is precompiled.]
   System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed) +3458850
   System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories) +125
   System.Web.Compilation.BuildManager.CompileCodeDirectories() +445
   System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +448

[HttpException (0x80004005): The directory '/App_Code/Reports/' is not allowed because the application is precompiled.]
   System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() +57
   System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +612
   System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters) +456

[HttpException (0x80004005): The directory '/App_Code/Reports/' is not allowed because the application is precompiled.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3434991
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +252

Does this mean that I cannot use the precompiled application option? I'm not sure how to turn that off in Visual Studio. I almost always use it. If I don't use the precompiled option, won't the source files be copied to the website? I usually use the precompiled option so that the source files are not on the website.

Any thoughts or help?

Thanks

 
New Post
12/10/2006 3:53 AM
 

first.. forget about the vs2005 publish function. You cannot just create new modules and than just copy them to your live server: the modules wont be registered that way, and you wont be able to do that. At the very least you will have to sync your db as well....

The best you can do is to create regular PA installers for your modules and just install them on your live server


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install to remote serverInstall to remote server


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