Nah, Mike I'm probably in need of some cheese with that whine. :) No, the install package is on the D:/drive in a folder set up specifically for this site and IIS is set to target it.
I'm used to the old way. Apparently the DNN install is put in a folder AND under inetpub/wwwroot/ and I have no idea why.
I've set up:
0. Unzipped the install package to a folder on the D:/ drive. (I had tried the source code package earlier, setting up release.config and renaming it. It didn't fly so I put the folder in recycle and started over with the more recent procedure at the link below)
1. App Pool and IIS, included IIS APPPOOL/appName in Security with Modify permissions
2. I've set up a user (SQL Login) and NTAUTHORITY/SERVICE I believe it's called in SQL 2008R2
3. Set up the web.config with connection strings and so on
4. Basically, set up everything "pre-6.x style", tried browsing to http://localhost/sitename/install/install.aspx?mode=install and no go.
All other sites are set up this way and they run fine. I prefer the path setup of d:/sitename/website/ and not having all site folders in the root folder. This is just for consistency sake and also because I usually install the source version. It's handy to have in the same application if you want to create a module and use some DNN functionality.
I suppose I should "reboot" my installation way of thinking? Just use the new style? I'd really prefer the procedure for the full source install, not the "install only" if that's apt terminology.
Thanks,
Mike