I'm running Windows 10, IIS 10, VS 2015, SQL Server 2016. IIS App Pool is using the Network Service as an identity.
Here is what I've posted on VS 2015 Forums:
I have 2 machines to keep my educational work separate from my business work. On both, I now have VS 2015 Professional installed.
On the first, I'm able to build the DNN 8 Source solution just fine. Then browse to the site with Chrome and Dot Net Nuke does it's thing and installs. The website can be accessed.
On the 2nd machine, this gets complicated. I tried the build first with VS 2017 and the DNN install worked but I could not browse to the site. Eventually, I just copied the Website code and DB from the other machine to other and it works.
For the 2nd machine, here's the sequence of events:
- With VS 2017, built the solution which seemed to go fine
- Browsed to the site and got a nebulous Dot Net Nuke Error, was able to find what was failing. A file could not be located in the path so the site broke, basically. Could not fix it by tracing down permissions, etc. So ...
- Uninstalled VS 2017, installed VS 2015 Community and set everything back up. Got the same error.
- Uninstalled Community and installed VS 2015 Pro. Built the solution, got the same error.
Backed up the DB on the working machine, zipped up the working website content. Set up the Db on the new machine and replaced the /website folder content. Bravo! Could now browse to the site. However, this replaced the former /website content for the Visual studio solution's original /website content.
Now when I build the solution I get 10 errors, all from the DotNetNuke.Website project. They're all errors that complain files can't be found. All the files are in Solution Explorer.
Copied the path of one of the files from one error and sure enough, in Windows Explorer I can browse to the location and find the file is there. Checked permissions, these are correct.
OK, somehow there are build errors happening that I can't track down. I can copy all the solution code over from the machine where the build / DNN install worked but really, I need to find out what happened to the process on the non-working machine. It'll just sneak up and bite my hind quarters again if that isn't located.
If possible I'd like to skype-share, go to meeting, etc. with someone to track down what's up. Or if this seemingly complex scenario has a simple solution and anyone sees what it is, info me. I sure don't see it. :)
Thanks in advance -- this is a tough nut to crack, I think.
Here are screen shots to show Visual Studio should know the files are there. This is the error window:
Here is the solution explorer:
Here is the Properties window, clearly showing the correct path to the file: