Visual Studio :: Debugging With Development Server Initialization Slow?
Apr 25, 2010
Debugging using the ASP.NET Development server is extremely slow to initialize. The behavior I'm getting is that if I launch the DevServer from VS2008, the first attempt to load a page takes minutes. After that, it's fine. Before the first page load, the DevServer UI responds to input normally (I can bring it up from the status area, use its context menu, and move the window around) until the first page load comes in. Then it shows the busy cursor (spinning blue ring) for 2-6 minutes before finally completing. There is no significant processor or I/O activity during this. After that, it runs normal speed, quite fast.
I just started getting the error message "Unable to Connect to the ASP.net Development Server" when debugging a website with VWD 2008 (everything was fine in the past). My system is Windows Vista with Windows Live OneCare firewall. I have reviewed other postings related to this problem, and they indicate firewall setting problems - settings not allowing VWD internet access. However, my settings on the "Windows Live OneCare Firewall Advanced Settings" tab specifically allow VWD.
Overall debugging works, but each step through code takes dosens of seconds.
I've already closed all additional windows like stack trace,watches,autos; deleted all breakpoints.
server and dev machine are located in different domains, so i set up local user on both, with matching password. remote debugger is running as service.
looking at security log, I found quite a lot of entries about remote debugging account logging in (record about every minute).
how i can speed up remote debugging?
dev computer: quad core, 8 Gb mem, win 7 x64 , visual studio 2010 ultimate target server: asp.net website , 2xdual core xeon, 2Gb mem, remote debugger 2010communication channel: vpn , 5 mbit , latency about 20ms. (seems that debbugging never uses more than 20 kb/s)
I recently upgraded to Windows 7 Ultimate on my work computer. Before this debugging a website in Visual Web Developer 2008 was really fast - the page loaded up like a normal website would.
Since I've upgraded to Windows 7 the page loads like normal but gets stuck for about 30 seconds at the end of the load - this is slowing me down as I normally need to use the FireBug tool as soon as the page has loaded.
In Visual Studio, when I click > Debug, > Start Without Debugging, (with my default browser set to IE), the application starts but it opens 2 IE browser instances. It opens 1 IE instance to start BUT when I close it, it launches another browser instance with the same start page. This bug is repeatable and consistent behaviour, that I can reproduce on-demad in IE.
(In some other minor variations, it seems that depending upon exactly how I start it, it will open 1 browser instance with 2 tabs, each tab having the startup page in it. However, this is not yet repeatable or consistent. It has happened; but, as of now, I am uncertain as the the exact steps to reproduce this particular variation of the anomaly.)
I am using Internet Explorer 8 (IE8).
I am using on Windows 7 32-bit.
I am using Visual Studio 2008 Standard.
I only have 1 startup project defined in Solution properties.
I have all Toolbars And Extensions set to "Disabled" in IE.
I have turned off "Automatic Crash Recovery" in IE.
I get this error when I hit F5 in VS 2008. I have checked that Windows authentication is enabled on the site and it is. I can mannully attach the debugger to the IIS process and it works. What could be wrong? I have tried alot of things without success.
I'm trying to debug my web application on my localhost machine in Visual Studio 2010 and I keep getting this error: "unable to start debugging on web server. The Microsoft Visual Studio remote debugging monitor(MSVSMON.exe) does not appear to be running on the remote computer."
Is there a way I can turn this off as I'm not trying to make any attempts debugging remotely.
I have my local Dev environment VS2K8 (ASP.NET) and our Dev server with no Dev tools. I have an app that runs just fine locally, but once I move to the Dev server I get an error. Another part of the problem is that I am moving the compiled dll for the website so I am not even getting the .cs line in the event log so it is very difficult to debug on the Dev server.
I'm a .NET specialist working with a PHP/Flash programmer to deliver an app via IIS. After jumping through 17 hoops of fire and defeating a gargoyle in a gruesome battle to the death, I managed to get my IIS 7.5 server to cooperate with PHP, and now if you browse to my public web site, you can see the Flash objects happily doing their behind-the-scenes stuff with PHP, whatever that may be.
But... when I'm debugging my app using the VS Development Server, that still apparently doesn't know how to cope with PHP: I'm getting the same HTTP 405 (Method Not Allowed) errors that I was getting on IIS before aforementioned gargoyle breathed its last ("The HTTP verb POST used to access path '/php/blah.php' is not allowed.").
So, what do you have to do to get the VS Dev Server to play nice with PHP?
When debugging my website project I usually go to start options in the web project's properties and select 'Don't open a page' and 'Use custom server' with a url that's in my host file pointing to my local IIS.
Even when I do this though visual studio still spawns it's own Development Server instance every time I hit f5.
Also for web application projects that have shared ascx files for instance Visual Studio will also launch an instance of Development Server each time I debug the solutions for each for these projects. This results in a million instances of Development Server running on my machine at any given moment.
Is there any way to disable development server for a given project completely? Without pointing it to a localhost sub application?
I'm getting "Cannot connect to ASP.NET development server" almost every time I stop the ASP.NET server before restarting the project in debug mode. It can take between 15 seconds and 2 minutes to get the error message, and Visual Studio is frozen.
Sometimes I get three in a row, and I have to wait 2 minutes each time, or go into Task Manager and kill to process. Then I have to start Visual Studio 2010 again, which is at least three times slower than Visual Studio 2008 to open.
It's *extremely* annoying. I know I don't have to close the server if the code has changed, but sometimes I simply want to restart my website in debug mode (there is a cache on most web service calls, so this clears the cache). A workaround is to add "foo" code to a class and restart the project.
I'm running Visual Studio 2010 Professional on Windows Server 2008. I'm running the Visual Studio Power Tools too, with the latest update.
Under IIS I would have to do a special configuration to support PHP. I have also found a number of references related to previous versions of VS which state that the development server would not, hence my question. Will the development server run the following PHP script server side in the header? Are there special configuration requirements?
A number of developers trying to create Silverlight apps intergrating Facebook have ran into the same wall with the MS Facebook SDK, and are struggling to determine the cause. I am assuming the script file contains the integration functions.
i want to know how do i deploy ASP.NET web applications on client machines which runs with the visual studio development server rather than configure it in the IIS on the client machine? I know its possible and telerik also uses this approach.
I'm getting this problem with one of my web projects. I've looked at [URL] and other suggestions around the place, none of which apply here. The odd thing is, it's occurring with *one* of my new web site projects, but not another one. Odd again is that they're both 100% fresh sites, created with the "New Web Site" option in the File menu, within a day of each other, and nothing has been done to them, apart from a bit of "hello world" html. WebSite1 was created first, and Cassini worked when I first created it the other day. A day later, I created WebSite2 and Cassini worked (and still works) with that one.
However, when I open WebSite1, I get the above error code - again, it was working fine the other day, and WebSite2 works fine. I've compared their .sln file - so differences apart from the VWDPort number used, and of course the path to the site and various GUIDs. Everything else is identical. Same with comparing web.config files. No differences there at all. So I'm stumped - why would Cassini start up fine with WebSite2 (and subsequent sites I create) but suddenly stop working for the WebSite1 project, when it was working ok a couple of days ago?
I'm attempting to run/debug an ASP.NET MVC project under .NET 4.0 using VS2010's Dev Web Server. The server appears to spawn successfully and an instance of IE Explorer opens. However, the browser never seems to find the page. The browser just "spins" showing only a white page...no error message.VS is configured to randomly select a port, although I get the same results when configuring numerous static ports.The ASP.NET project is the start-up project.
ng an application that listens on port 25. My application will work as a SMTP server receiving emails. I am aware that I can just enable IIS SMTP feature, but for my current project, I needed to do in this way.If I can send emails to visual studio development server which has a private IP, my debugging will be much easier. Is there a way to send emails to VS development server?
When viewing an asp.net page in visual studio 2008, the asp.net development server icon shows up in the system tray. It can be stopped by right clicking on it and select "stop". In Visual Studio 2010, I do not see the icon any more. where the asp.net development server is? How to stop it?
I have a test website with VS 2008 that just uses code behind files, such as Foo.aspx.cs. Thus, the web server compiles them on the fly. The problem I'm running into is I can't use any C# 3.0 features. If I do:
[code]....
Then VS will work fine (everything gets highlighted and Intellisensed), but when I run the site it just throws up compiler errors..
Is there a way to fix this, or do you have to compile a DLL to target the 3.0 runtime? If so that's insanely lame.
Not too long ago I was given a new PC with windows 7 Professional on it. Before, I had vs 2008 running on win xp which worked OK. I started getting error msg (Unable to connect to ASP.NET development server) after I installed vs 2008 (version 9.0.30729.1 sp1 vs team system dev. edition) and ran one of my projects and even a simple test project. The first msg shows the syntax of webdev.webserver with an example in the bottom. I can get this error by running the project or by showing any page in the browser. I noticed that file WebDev.WebServer.EXE does not appear in the folder C:WindowsMicrosoft.NETFrameworkv3.5. If that's the only reason why I am having this problem than how can I fix it. I was told that .net framework 3.5 works on top of .net framework 2.0?! I just want to sort out this .net framework mess on my new machine. I am willing to uninstall all .net framework and start fresh. Another thing that I am willing to try is to get from a coworker the WebDev.WebServer.EXE (from the .net framework 3.5 folder) and see if it works.
I noticed a layout issue on the web app I'm working on, and in trying to correct it via the stylesheet I realized that the development server is not recognizing any changes I make to the .css file. As confirmation, I saved a blank stylesheet (which should have removed all styling), cleared my browser cache and rebooted my development machine and the original styling remained. It seems some version of the stylesheet is "stuck." The stylesheet is referenced in my master page, and the path specified is correct.
Now that I am playing with NHibernate I am getting a lot more YSODs as I am learning it however I seem to get this error sometimesafter a YSOD:This webpage is not available The webpage at http://localhost:49497/ might be temporarily down or it may have moved permanently to a new web address.Error 139 (net::ERR_TEMPORARILY_THROTTLED):
Unknown error.Is there any way to disable this because I have to wait a few minutes every time and that is a pretty big killer is productivity?
I am getting an error "Unable to start debugging on the web server..." while running as web application in VS2005. But the error seems only for this application. I created a test application, both in VS2005 and VS2008, and found no issues in running these applications.