Forbidden error in VS2005 under Vista for ASP

[tonydee61]

I have a web application that built on using VS2005 running under an XP operating system. Recently the computer was upgraded to Vista. After installing VS2005 and all pages, pressing the RUN button throws an error where the start page is "forbidden". I have replaced the page with a test page named "Test.asp" that merely says hello, and that does not display (access is forbidden). I haven't a clue. I am an administrator on the machine. Does anyone know what this problem is?
Thanks.

[tlhintoq]

Recently the computer was upgraded to Vista.

On purpose? Why? Just a tip... Forget Vista ever existed. It was all just a nightmare. Either stick with XP or go to Win7.

After installing VS2005 and all pages, pressing the RUN button throws an error where the start page is "forbidden".

Sounds like a huge shift you made without checking it out first. May I suggest that you get VMware? You can have virtual machines running on your one computer, and debug directly into those virtual machines. So you can be running Windows7 on your computer. Have a virtual Windows XP running within that, and Visual Studio can send your project to debug inside that virtual XP and still get all the debug information. It's great to be able to debug in 5 different O.S. without needing 5 physical PCs, or without needing to actually install Visual Studio into 5 machines.

May I suggest turning off the UAC? Then move the entire project out of your personal folder. Visual Studio by default saves in your personal folder. I never do it. I keep a directory at C:\Code for all my projects. Short path doesn't get hit now and then with "path too long", and I know this directory isn't being treated special, like a user's home directory does.

[tonydee61]

I will need to take some time understand you suggestions. This application was created 10 years ago under Interdev (VB6) under Windows 98 and evolved over that time. With each change, I have never encountered this type of problem installing and debugging.

[Frinavale]

Right click on the solution file and choose run-as administrator.
You can run Visual Studio as a regular user but you cannot debug unless you run Visual Studio as administrator.

-Frinny

[tonydee61]

When VS2005 is launched, it is launched as an administrator. When the "run with or without debugging" is started, I do not know what credentials are used after it starts. Problem seems to be rendering ASP instead of ASPX. I have been advised to change to VS2008. Not sure it is an option for me at this time, but a consideration.
Thanks.

[Frinavale]

That's a little weird.

Have you considered installing IIS and publishing the website there to see if the problem happens on a real server?

[tonydee61]

I have IIS 7.0 installed and enabled. I haven't tried to publish to myself (never had to do that before). I tried setting up 2 ways. (1) All files under c:\inetpub\wwwroot and an IIS application created. (2) Running with all files under Documents\MyProject\yada-yada. Either way clicking the RUN in VS2005 produces the same "forbidden" error. With option (2), under IIS, I can browse the start page to launch, but the error is different. This time I get an "object or with block not set". I suspect this is a result from running a DLL registered in COM+ which may have other permission problems. COM+ usually gets me when I load this project for a developer with XP. This Vista is truly bleeding edge for me.
Thanks.