I believe the name space and changes to the modules were not done. And also, DNN 4.02 isn't a release like 3.1.1 & 3.2.2 to my knowledge.

I think since you have had experience since DNN1, saying that it's not suitable for mainstream might mean that you should be using the most stable release which is either 3.2.2 or 3.1.1. 

There have been mixed reactions with DNN 4.02, from the installation perspective, but the distinct differences with dnn 4+ & 3+ is this -

If you require a VS2005 SQL2005 Development platform, then you need to work with DNN 4+ as it's written to work on aspnet2 & uses the namepace structure required to work in VS2005 which I believe works only with SQL 2005.

But DNN4 will install on SQL2000 without any problems.

With 3+ installations, I've not had any problems with it, and I'm not saying there aren't any, but the 4+ installs have brought about alot more install questions for those who are using 2005, 2000, sql express, not knowing you can't develop in 2003.. the list goes on.

Is there any reason you need to use 4.02?  I regard working on the bleeding edge too painful these days, so work only with 3.2.2 and while I've had issues with memory, it's been a fairly good build.  

I'm sorry to hear you have these problems - to work with something for days is so frustrating, I sympathise with you from the point of view I also have had days, in fact on my own site, weeks of trying to get it right and when you've taken the step forward, there is at times, no going back.

There are no extra modules installed with the 4.02 build. You can see what gets installed by looking at the install/modules folder - check out the different modules compared to 3 installs.

The key things I see stopping people to get a successful build running is they don't know how to configure the web.config file to install dnn4 which has two points of config modification and the string is slightly different when using the sql2000 install.  I've not had problems with it locally but not been able to get dnn4 running on my 2000 server so have not bothered for now until i do more research.

I woudn't bother trying to repair the install. I've found that if you are starting from new with the onset of problems, just drop the whole db and folder and start again. 

Have you tried locally to get going or do you not have option?

Nina Meiers

Nina,
Thank you for your reply.  I finally got the site running.  Would you believe that the biggest problem was the FTP?  The files, even at the binary level were truncated.  How's one suppose to deal with that?  I resolved the issue by completely wiping out the site.  I had only 1 FTP transfer that was the 4.0zip of dnn.  I had the hosting company unzip it (I left a copy of web.config and didn’t overwrite it upon unzip.  WHAM! the site came up.

Now, I'm trying to create a PA and package WebHarpoon.  There are significant enhancements I made.  WH has been converted to Dnn4, tested, retested, and ready do go.  but go where? how? huh?  I'm clueless on packaging on 4.  S. Walker's tutorial was a great start (using the starter kit) for porting to 4 (WebHarpoon), but falls way short of actual deployment.  Does anyone have a DNN4 module deployment tutorial?  (A video would be very sweet.)

Thanks again Nina... Some day I'll get to know how to do a skin (if I ever get WH published.)