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
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Really really simple (maybe) installation questionsReally really simple (maybe) installation questions
Previous
 
Next
New Post
11/8/2007 11:33 PM
 
hostricity

Joined: 11/8/2007
Posts: 2

I want to install DotNetNuke on commercial Windows web host. My objective is to install the CMS successfully, configure it, and then play with it to determine suitablility for various uses.

.net 2.0 and MS SQL Server 2000 Enterprise are installed on the server.

I can't seem to find any documentation that makes much sense to me.

It seems like I should

1. Create a database

2. Upload the Install kit to the root for this domain

3. Run an install script from a web browser

I've spent several hours looking for documentation and everything I've found doesn't quite tell me what I need to know.

Is there some basic documentation that provides this info? I can't find it, and I don't understand what I have found. (I'm a programmer with lots of experience developing systems to run in this environment, but I haven't tried to install a pre-written package before. When I've installed my own applications, it has been a snap since I knew how they were set up.)

Questions I would not have thought to ask if I hadn't seen references to these items while searching the DotNetNuke website:

1. I see that the database is supposed to be named DotNetNuke. Does that mean the database name can't be set when dotNetNuke is installed on the web server? How would you change the name of the database? I ask because naming the database DotNetNuke appears to be important to the installation and that seems like it would be a simple configuration, not hard-wired to a particular database name.

2. I see references to installation of Visual Studio, etc. on my local machine. We have all of that, but why do I need it on a local machine to upload and install the dotNet CMS application to a remote webserver and configure it?

Finally:

I haven't found anything that discusses features from one version of dotNetNuke CMS to the next. So, I am wondering whether I should try the just released 4.7 or if I should use 4.6.2 or 4.5..5 due to the use of SQL Server 2000 Enterprise instead of a newer SQL Server. Ease of installation and stability are more important at the moment than any other factors.

Geoff
 
New Post
11/9/2007 10:38 AM
 
Brian Dukes


Brian Dukes's Avatar

Brian Dukes's Avatar

www.engagesoftware.com
Joined: 8/25/2006
Posts: 896

Have you read the DotNetNuke Installation Guide?  That seems to be pretty complete.

You can name your database whatever you want.  Also, DNN should be fully compatible with SQL Server 2000.  So far as features go, the best way to see what's new in a DNN version is to check out the Change Log for the main DNN project on Support.DotNetNuke.com. 

Our typical install procedure is to unzip the install package, give the ASP.NET Worker Process ACL File permissions to the website (the ASPNET account in IIS5, NETWORK SERVICE in IIS6 & 7).  We would then copy the release.config as web.config, and then set the connection string to the database (in both the connectionsStrings section and the appSettings section) in the web.config.  I believe you could also skip the step of setting the connection string, and the installer which runs when you first hit the website will let you set it.

At that point, you just need to make sure that IIS is set up for the website, and hit the site.  The installer should run and leave you with a working DNN portal.

Hope it helps,

Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
11/9/2007 10:39 AM
 
Brian Dukes


Brian Dukes's Avatar

Brian Dukes's Avatar

www.engagesoftware.com
Joined: 8/25/2006
Posts: 896

Also, you shouldn't need Visual Studio on the server.  You should only need Visual Studio if you are doing custom module development.

Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
11/9/2007 12:41 PM
 
hostricity

Joined: 11/8/2007
Posts: 2

Thank you.

The Installation Guide only covers local installs, not installs to a remote web server.

Also, it is dated 2006, so I didn't know if I could trust the information anyway.

You provided the information I needed - I can't find anywhere in the documentation where it says 1) set connection string, 2) upload to domain root, 3 go to site.

Thank you. It always amazes how the most basic information is hidden away where only the high-priests can find it. For example, I haven't found any documentation that specifies the host server requirements.

This is why we try to talk our customers into using one of the CMS packages we are already familiar with - on those, where we have already gone through the hours of pain and inadequate documentation, we can install in 5 minutes (plus the time to upload the code).

I'll do as you suggest.

Thank you, again.

Geoff 
 
 Page 1 of 1
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Really really simple (maybe) installation questionsReally really simple (maybe) installation questions


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