No need for the lecture, I realise it's a free platform, that's why THE LEAST OF WHAT I COULD DO, is report an issue that might affect new users, if instead of;
1. setting up a standalone IIS Express and running the install.
They.. 2. open a Visual Studio web folder "that includes IIS Express automatically" AND kicks off their development environment - yes I realise, not the silo'd module dev environment dnn officially recommends.
Anyway I'm choosing option 2, all day every day!
Comparing it to an ISO installer is a bit of a stretch, as 'IT IS' the website folder and continues to run on the IIS server. Shipping some parts packed and others not and relying on the packed parts.. sloppy, imo.
For the prevalance of the option 2 workflow in .NET, I would submit a pull request to address this, or even just a 1-sentence note in the setup guide to turn off full compilation in VS, if you rebel and setup IIS Express that way. But I am certain it would fall on deaf ears and anyway I have since decided to go another way as far as upgrading my legacy dnn site is concerned.
Good luck to the next VS guy, sorry we probably could have just fixed this in the time it's taken to have this chat ;-P
These Forums are for the discussion of the open source CMS DNN platform and ecosystem.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.