Looking for DNN4 stuff??? Check my more recent posts:
* DNN4.02: Create Your DotNetNuke Development Environment
* DNN4.02: Quick & Dirty C# and VB Custom Modules
* DNN4.02: Starting New DotNetNuke Modules in C# or VB.Net
UPDATE: I'm getting tons of hits on this from Google, as it turns out, this one of the most authoritative posts on installing DNN3. That's great to hear, but I threw this together for myself to use later, I know it's not as good as it could be.
PLEASE PROVIDE INPUT
Any details I may have missed, better verbage, etc... Please post any new updates to DNN3 that change process below so I can keep it up to date... I'll be watching, thanks! - Gerry
DotNetNuke 3 has been in the blender for months now, and I've passed up a dozen (almost) chances to play with betas, but real life has kept me from seeing what Shaun Walker et. al. have brought our way. Well... it's finally out, so I decided to dive in and check it out myself.
For those of you (like myself) that would rather muddle around with the source instead of using the good old rtfm method to get it to install correctly, here are some pointers. For reference, I've installed it to my test folder dnn3, mapped to http://localhost/dnn3.
Update June 28, regarding the v3.1.0 release: There is now a selection of .config files, no web.config comes out of the box! You need to rename release.config to web.config, after backing up the old web.config if you're upgrading. Also, if you're upgrading, make sure you retain the MachineKey values in AppSettings.
Let's get started...
1. Register at www.dotnetnuke.com, and download zip
2. Unzip contents into c:\inetpub\dnn3
3. Create SQL database “dnn3“, add user: dnnuser as dbowner
4. Update .sln file's 2nd line, the web project web path from the default of “http://localhost/dotnetnuke/etc“ to “http://localhost/dnn3“
5. Update sql connectionstring in web.config
6. Make sure your IIS user acct has privs to create files & folders in c:\inetpub\dnn3 (read instructions for detailed priv requirements to lock it down!)
7. Browse to the site http://localhost/dnn3, installation will commence
Note, if the install fails at step 7, you're best-off removing the db, and the folder completely, and restarting the process. If the install processes fall out of sync, it's a pain to recover from. The step 7 problems I had were due to messing up step 6. I went to the instructions to get detailed priv info for my iis acct.
Next - I have some observations to make...
Telligent's Community Server takes a few less steps, and is much easier on the non-geek trying to grow a social-network:
1. download the install.exe
2. double-click the install.exe
3. Do what the wizard says.
Us geeks on the other hand get a thrill figuring out how to iron out the wrinkles of an open-source deployment...
Also, on dotnetnuke.com, there's news of “dotnetnuke sub-projects”, which strangely incorporate only Weblogs, Forums, and a Gallery at this moment. For those of you following Telligent's Community Server, you will notice an obvious parallel. I have been with DNN for a long time, and I'm also a big fan of Telligent's work. I have to wonder why these two didn't pull their acts together and share the skill they both obviously have. It may have something to do differences between licensing agreements & commercialization.
Anyway... the install is complete, and I'm staring at a beautiful, rich DNN interface that blows the socks off DNN2.
Multiple super-user accounts
Drag & drop modules
Modules decoupled from the core
Module content XML Import/Export
That's in the 1st 2 minutes of looking around. Time to recompile all my custom modules to version 3 now!
Print | posted on Monday, March 14, 2005 10:59 PM