I am perplexed to observe that nobody apparently reports problems in using 4.9.4, 5..1, 0, and 5.1.1 Install and Source packs.
I tried dozen times and could not get website running from Install pack in VSTS2008 (Visual Studio Team System) File System (only succeded as Local IIS websiteprojects, WSP)
and couldn't get it from Source packs using both File System and Local IIS WPS.
Essentially I tried almost all possible configuration combinations except that I always renamed development.config into web.config
(I had never tried release.config). And I could not get them straight by Install guide
Eventually I found workaround with which I succed installing both from Source and Install packs in VSTS as both File System wsp and Local IIS wsp.
Instead of renaming development.config to web.config from its own (Source or Install) pack,
I am copying web.config from already successfully installed DNN websites using Starter Kit(s) templates.
(And during in the latter installation I renamed from its development.config)
After that I proceed with installation (Ctrl+F5) from Source or Install packs.
Sometimes it requires quite obvious simple tweaking in web.config due to surfacing erors
much more obvious than getting broken website without any errors
and/or necessity to know intricacies, histories and bugs of DNN development
NB
that I take web.config of already successfully working DNN websites (from Starter Kit) and not from web.config (or developer.config) before installation
and, then, I proceed with installation (CTrl+F5) stepping
I just wonder why nobody else are bumping in the same problems as I am???
As I understood, I should manually configure web.config while installing from Install and Source pack, should I?
And this requires pretty thorough understanding of all intricacies and bugs in DNN...
What is the sense of using Install packs in comparison to Starter Kit templates?