Hey,

I've been an ASP developer for the past 6 years, and was struggling/failing to build a similar CMS when I saw the DotNetNuke demo video and wept.

But I'm scared of change -- I've never used .NET at all -- especially when it involves messing with my W2k3 server, which is currentlyhosting 30+ client sites. I want to start using DNN, but am apprehensive about inadvertantly screwing up what already works.

Questions:

1. Do I need VWD or Studio installed on the hosting server to install DNN 4.2? Or would these only be necessary if I wanted to develop modules/edit the source code? If so, could I only install those locally and not on the server?

2. Does installing DNN in anyway affect other sites already running on IIS 6 or using SQL2000 Server? (I've installed ASP components in the past that have stopped IIS during install and failed to restart it when finished, so I'm gun shy about this stuff).

3. Would it be better to start with just a DNN hosting package to get used to using it, before deploying on my own server? I'd like to have access to a customized menu of modules without worrying about what a hosting provider allows me to use.

I'm sure I'll have more questions, but the prospect of using DNN is very exciting to me, if I can overcome my natural fear of screwing things up. Thanks.

"2. DNN doesn't affect other sites, it's simply an ASP.NET application. To learn more go to ASP.NET and take the tutorial."

I humbily submit that while "DNN doesn't affect other sites" the contortions and changes you make to directory PERMISSIONS may/will affect other sites, other applications, your ability to apply vendor maintenance, etc. as you try and get DNN to work.

Always accurately record all existing on each directory's/file's permissions in the entire directory structure you are altering BEFORE you make any changes.  Beware the "Replace the permmission entries" checkbox; Use the "Inherit from parent" and copy the existing permissions, while adding your own.