Sanjay Mehrotra wrote
I just tried your scenario but using Source version in both cases and I was able to get the site up and running without any problems. Can you try either the route of using just the source version (start from scratch - unzip source version, create virtual directory, rename release.config, point to blank db and navigate to site)....
Or the other option could be, could you send over an email with exact steps and screenshots - maybe I'll see something in that which I'm not seeing via your post - email should be visible via my profile.
Thanks
Sanjay
Hello again, Sanjay. I'm back to trying to get the source code version functional. I just finished following the instructions you gave (above), navigated to the default.aspx page in IIS and the scripts ran fine. It worked great.
Until I tried to load the project in Visual Studio 2008 (you KNEW this was coming, right? ;). When I try to load the solution, VS says, "Unable to open the Web site 'http://localhost/DotNetNuke_Maintenance'. To access Web sites on the local IIS Web server, you must run Visual Studio under an Administrator account in order to have access to the IIS metabase. Alternatively, install FrontPage Server Extensions 9FPSE) and then gran FPSE access to users who will run Visual Studio."
Then, once I dismiss that dialog, I get the message, "The project location is not trusted: C:\Inetpub\wwwroot\DotNetNuke_Maintenance\Library" etc. for each project in the solution.
Problem is, when I am logged in as Administrator, I still get the same message.
Any idea why this is and what to do about it? It seems I'm mighty close to being able to use the source code version - if only I could now get it to load in Visual Studio.