Me too. Install and set up of DNN 7 in a development environment has cost me 2 days. DNN 6 took me 5 minutes.

My understanding is that it is true to say that we don’t support building and running the source package using IISExpress without making any changes, as our solution out-of-the-box is not configured for IISExpress but for IIS i.e. the default sln contains a path such as localhost/DotNetNuke_Community – these kinds of url paths require IIS, and are not supported in IIS express. I believe editing the sln file and using an IIS express based url e.g. localhost:3456 would resolve this.

In addition if you are starting debugging in vs.net then I believe it deploys to cassini (visual studio webserver) not IIS Express by default, and cassini similarly does not support those type of paths. I think you can again edit the sln settings and set IIS express to be the default server, so if you have done the sln file changes that scenario will work also.

I believe we are investigating whether we should make these changes in the default sln file (or perhaps ship with a 2nd one that supports IIS express by default)

Note: hosting of DNN (i.e. install, upgrade packages) within IISExpress works as it always has - these scenarios only apply to users who attempt to use the sln file

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

the information came from an internal discussion that we (engineering) had a while back, so is not version specific (it was tested with a 7.x release AFAIK) - I don't have information on what OS and whether UAC was in place (i.e. was vs.net ran in administrator mode), but I'll pass on the details.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US