OK, so the install docs are just almost 3 years since last update. Not good.

The brief, one-sentence descriptions given the current 4.9.3 release really don't quite do the trick.

For example, the "Install" package says it is for "run-time deployment". The "Deployment" package says it is for "Installation" 

Uh... anybody see a problem there?

And then there's the "Starter" edition, which is to "configure a development environment in". It doesn't mention VS2008 at all, yet obviously from other posts here, it should. And except for the full source edition, the "Starter" is the largest of the installs... making less sense.

So the starter is for a configuring a development environment... for what? To develop modules for DNN? Do develop a website using DNN?

I'm disappointed that with the huge interest in DNN and the huge installed base, that even basic communications remain so uninformative. Even the PDF installation manual -- 3 years out of date if the "last updated" date is to be believed (and if NOT that old, then once again, why are communications so poor as to allow misinformation like that?) -- even the PDF itself seems to have prepared to provide the least amount of convenience -- the TOC isn't even linked to sections, so that you cannot click on the TOC entry. This is usually default.

So guys, what's what here? And please don't assume the section, "Which package should I use", from the docs, is sufficient, as it completely omits the "deployment" package (which, as above, is apparently for installation, whereas the install package is for deployment....)

Further, the section in the docs actually doesn't answer the question, nor provide the info needed to answer the question, "which package should I use?" -- it just says, basically, whether source files are included or not, and that the "starter kit" has templates for projects (for...? who knows), modules and skins. Sounds interesting, but ...

What's needed here is which version is targeted to what type of application or use. For example, I want to develop a website, based on DNN. I do not plan on developing code, as the website should be workable with built-in modules and possibly some custom modules I can buy, as it is entirely just content-managed information (and I am an experienced DNN 3 user, having successfully done 2 major sites with it, so I know what to expect at least).

So what's the deal here? I'd love to use VS2008 to develop/deploy the site itself (because of sourcesafe integration, among other things), but do I get any advantage from that if not developing code as such?

Should I deploy the install version? Or install the deploy version? And WHY?

Thanks for any clarification, and maybe such clarifications could make onto the info or download pages?

Hallo Karsten,

here is the usage of packges:

• "default" should be install package, if you want to run DNN on your pc or server, develop modules or skins
• if you want to test VS2008 starter kit feature, use DNN starter kit. I prefer to use starter kit for installation of module and skin templates only
• if you are a developer and want to check out Core Framework source code, use source package for install (and subsequent upgrades)
• to upgrade any non-source versions use upgrade package
• deploy package is for use inside customized versions of Microsoft Platform Installer

If you want to testrun DNN locally on your pc, the easiest option should be Microsoft Platform Installer 2.0 (beta), check out www.microsoft.com/web

If you want to test run DNN without installation, create your own temporary site at demo.dotnetnuke.com.

Hi Karsten.

Now i have to give my comments as well, as i understand your questions. At least partly.

* You're right (and i think the most here will agree) "StarterKit" is not the best name for the development package.
* Go with Install Package (you need xp or vista with activated iis, dotnet2 framework and sqlexpress. period)
* then you can develop your webpage, create skins and even modules (with visual web developer, its free, too)
* if there will be a newer version of dnn take the upgrade package, install it over your running installation and you have made your upgrade
* MS Platform Installer is a project where they are trying to build a meta-installer around web-packages (like DNN) and which should install all needed stuff around it what you need, instead of manual installation of 3 or 4 packages (sql, dotnet2, dnn....) got it?

Now, why i stated "at least partly" at the beginning.

* When you have a look at the download area here on the site, there is a good explanation of what is for what
* DNN as a Portal System (or CMS?) is not a small tool like Notepad. You have to read some stuff beforehand.
* Allthough the install-doc is 3 years old, it is still valid and possible to get dnn up and running with it, as long as one knows a little about internet-tech on microsoft

This is in the first line an open source, therefore more than cheap, system. We users here like to help each other with problems and i got help in the past as well. But don't expect that someone comes over and starts with "bees and flowers". A little bit of work on your own (the forum, especially the search funtkion) is a great pool of knowledge. This is what all here are expecting from new users: if you have read enough and still stuck with something, then ask.

I started with DNN 3 years ago without any huge probs so far (check my posts), and it is much easier then it would owe a long thread like that.

Have fun, good luck, but be proactive, not reactive.

Cheers

Kai