I have a C# MVC project created in Visual Studio 2010 Professional (VS) on Windows 7 but I am not able to run it and debug it in VS.
VS gives me: Unable to connect to the ASP.NET Development Server
The development server starts tho on http://localhost:63785/ but that gives me Server Error in '/' Application. HTTP Error 403 - Forbidden. Version Information: ASP.NET Development Server 10.0.0.0
I am able to start the application directly using: "C:\Program Files\Common Files\microsoft shared\DevServer\10.0\WebDev.WebServer40.EXE" /port:8080 /path:"D:\visual studio 2010\Projects\MvcApplication1\MvcApplication1\ but I am not able to use VS debugging that way
My colleague tried to run the application using IIS but that gives him the 403 error as well.
I dont have much experience regarding IIS or ASP, I tried to google it and tried few ideas but none seems to be working for me.
I had this problem once in firefox when the following checkbox was activated:
(Website right click in solution explorer)->
Property Pages->
Start Options->
Server / NTLM Authentication
Maybe you accidentally restricted access to all pages of your project? Check authentication / authorization sections in web.config
Related
When I try to run IIS EXPRESS in visual studio 2019 I get the following error message:
error message
And I try to move folder asp.net code, repair program, Uninstalls and install agian but I still get the following error message
Did you debug your application from IIS or IIS Express? If you are using IIS Express, I suggest you refer the link below:
IISExpress 8 Cannot read configuration file redirection.config.''
And it may also be related to your permissions, I recommend you to run VS as administrator.
I just installed VS 2013, and I cannot find an option to use IIS express when I right click on the website project name.
Did this option get moved?
Without this option when I open an existing website, and run, I get 403.14 Forbidden error saying
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
I'm new to visual studio 2013, would appreciate any help you can provide...
Open the Project Properties, and go to the Web tab. In the Servers section you should see a dropdown with three options: Local IIS, IIS Express, and External Host.
See Web Servers in Visual Studio for ASP.NET Web Projects for more information.
I cannot use VS2013 due to the fact that the "Visual Studio Development Server" option is missing. You can only use IIS Express, or an external host. When I use IIS Express, I get one of several errors when I launch a website with F5.
Failed to register URL "" for site "" application "/". Error description: Cannot create a file when that file already exists. (0x800700b7)
Cannot process request because the process (8204) has exited.
Neither of them make sense. I tried deleting all the configured sites in the IIS express config. I tried reinstalling IIS Express, Visual Studio. I don't see how the first error can occur. In all the demos I've seen, you can just hit F5 in VS and it works. This isn't the case here.
Right click on the Project in your solution and pick Properties.
Select web on the left side.
Choose IIS Express
Enter Project url
example:
https://localhost:44300
or you could check 'Override application root url' and type url like above
I have a classic ASP website deployed over IIS.
I am opening that website from the same location in visual studio 2010 (in order to debug, as per the steps mentioned here
The problem is that, when I hit F5 in visual studio it is giving me an error saying "your server does not support debugging of asp net or atl..."
I am able to browse the site from IIS, but I want to open it in Visual Studio in order to debug it.
What could be the possible reason and solution of this issue?
F5 doesn't do anything good for classic ASP sites (f5 will try to compile a .NET site and then access it).
I will assume that you are trying to debug the site on the same machine where it's running. The way you debug "classic" ASP using Visual Studio.NET is by attaching to the process running the site. The easiest way to do this is to use the Just In Time (JIT) feature: insert a stop statement in the code (debugger in jscript) - hitting that line should initiate a server-side "Error of type "Script Debugging" was encountered. Do you want to debug?" dialog, with suggestions of available debuggers to use.
Try this and report what happens - there might be some extra steps needed to configure that machine.
Are you using IIS 7?
If so you should the server option "Enable server side debugging"... It should be in the properties window of the site, using IIS Management Console.
Once you do that, when you run the server through Visual Studio, it should open another solution on debugging mode with the relevant code.
I just set up my machine to code Windows Azure apps in Visual Studio 2010. I have a machine at work, which works fine. The machines are both 64-bit Windows 7. I run as administator at work. At home I installed most of the VS and .NET components as normal user, but I'm running everything now as administrator, because I assume there could be some errors correlating to that.
Creating a standard Azure project with one web role gives me this:
"there was an error attaching the debugger to the IIS worker process
for URL http://127.0.0.1:5100/ for role instance 'xyz'...".
I searched Google 24 hours and tried most of the solutions, but none worked for me:
repairing .NET 4.0 (I didn't uninstall it prior to reinstalling, but
I will try to do so now)
setting the WebRole as Start Project works fine. It runs the webpage.
<system.web> <compilation debug="true" targetFramework="4.0" /> is set to true ( http://www.google.de/url?sa=t&source=web&cd=4&sqi=2&ved=0CDgQFjAD&url=http%3A%2F%2Fstackoverflow.com%2Fquestions%2F4541593%2Fazure-error-on-starting-with-multiple-web-role-projects&ei=RAhOTq27Fsv4sgaB_LSVAw&usg=AFQjCNFa6NveaRmUhBtEIus9vwK54VojKA)
there's no httpModules to delete ( http://natacha-huguet-millot.tumblr.com/)
there's only one v4.x directory in Windows\Microsoft.NET\Framework64 ( http://social.technet.microsoft.com/Forums/en-US/windowsazuredevelopment/thread/45e01c3d-7c16-4ca7-999b-46cb20b38c1d#0c118416-484a-413c-bd18-049033b1ccb8)
running aspnet_regiis.exe -r. succeeds but doesn't work ( http://www.dotnetspark.com/kb/3720-error-attaching-debugger-windows-azure-sdk.aspx) neither does rebooting
looking for Visual Studio Web Debugger log shows this (also my section name="httpErrors" overrideModeDefault in IIS is set to Allow; source: http://dunnry.com/blog/2011/07/14/HowToDiagnoseWindowsAzureErrorAttachingDebuggerErrors.aspx):
http://127.0.0.1:5100/debugattach.aspx
Status code=403 (Forbidden) Protocol version=1.1 Cached=False
Content-Length=53 Content-Type=text/html; charset=utf-8
Date=Fri, 19 Aug 2011 20:16:48 GMT Server=Microsoft-IIS/7.5
X-Powered-By=ASP.NET
/debugattach.aspx-application debugging not activated.
When I comment out the Sites-Tag in the ServiceDefinition.csdef I get the following error:
"unrecognized attribute 'targetframework'. note that attribute names
are case-sensitive"
Here I also tried most solutions to be found on the internet:
setting the right .NET-Framework version in IIS-Manager (all application pools are set to 4.0, when starting the project, the error page shows framework 2.0 though, where can I change it?)
installing the newest .NET-Framework, I have 4.0.30319
None of them work.
If you have any advice, I will try it and list my result in this post.
I was getting this due the the properties on the azure project being set up incorrectly.
I had to change the setting from IIS Webserver to IIS Express
The first question to ask is which version of Windows 7 are you running at home? I'm going to go out on a limb and guess that it's Home Premium and at work you run Professional.
The catch is that with Home Premium (an lesser edtions) you don't have the option to install the necessary components to be able to debug in IIS. To confirm this, on your work computer go to Control Panel -> Programs and Features -> "Turn Windows features on or off" and have a look under the IIS option. You'll see more there than you do at home.
I have not found anywhere in the MS documentation on the differences between various editions of Windows 7 that this is the case. I'd be happy for someone to correct me on this though.
To get around this issue is while running at home to change the project to run with Visual Studio Development Server (right click your project -> Properties -> Web) and make sure that you change it back to using IIS before you check in your code.
Or you can buy an anytime upgrade for windows to Professional.
Got the same error and fixed it by changing the defaults for the app-pools in IIS.
Start iis manager
Select application pools
On the right side, in the 'Actions' panel click on 'Set application pool defaults'
Set .NET framework to 4.0
OPTIONAL : Set Enable 32-bit applications to true
This worked for me:
Go to IIS -> default web site -> bindings
Set the default http port back to 80.