Hi Ken,

Well I'm still stuck in the same place. I created a brand new database (DNNSource) and unzip'd the latest source version to c:\code\DNNSource. When I opened up the VS2008 solution file it wouldn't load the website project. It kept telling me I needed certain components installed and that I had to be running as an Administrator. I finally got all the components installed that it wanted (some IIS6 compatibility stuff and Windows Authentication) but it still kept telling me I need to be running VS as an Administrator even though I was. So eventually I gave up, deleted the website project from the solution and selected "Add --> Existing Web Site..." and added c:\dnnsource\website back in. However I still can't run the solution from VS. When I hit F5 the default page won't even launch. The browser tries to open http://localhost:49269/Website/ (I'm just using the built-in VS web server) and I immediately get "Internet Explorer cannot display the webpage". I really don't know why this isn't working. If I create a new website in IIS and point it at c:\dnnsource\website it works fine when I browse to http://localhost and I can create the database, get the default page, log in, etc. It just won't work from VS.

Any thoughts?

Thanks!

Phil

Hi Ken,

Ok, I figured out what the problem was with running from VS. I forgot that since the website was running under http://localhost:<port>/Website, I needed to add an entry for localhost/Website in the Portal Aliases table. Since I hadn't done that it was redirecting to simply localhost and (at that point) I had already shut down the IIS default site so there was nothing there. That's why I was getting the IE error.

The next problem I ran into was that I everything was working fine within VS, but after I did a deploy to our live server I could only get to the default page. When I tried to click on Login or Register or anything else I got a 404 error. After hunting around a bit I tried setting the URL rewriting in the web.config file from "humanFriendly" to "searchFriendly" and that cleared up the problem. Which is weird because a) I shouldn't need to do that, right?, and b) all the posts I saw that recommended using "searchFriendly" URL's were for the exact opposite problem (i.e., everything working fine in a deployed environment but not from localhost under VS). So... whatever.  At least it's working now.

Thanks for your help and suggestions.

Phil