I have an ASP.NET MVC3 web application with EF Code First. It's set up to debug using my local IIS (as opposed to the Visual Studio 2010 Developer Server). I also have Google Chrome set as my default browser.
If my repository layer uses the .Include() method, Chrome takes at least 10 seconds to return the page, usually more than 30 seconds. I can step through the debugger all the way to the View very quickly, and yet Chrome still takes that long to finish serving the page.
This problem goes away if I do any of the following
Take out the .Include()
Use IE or Firefox
Use VS Development Server instead of local IIS
I have no idea why this would happen, or how to further troubleshoot it.
Turns out it was the Glimpse NuGet package. I disabled it in my web.config and it works fine now.
Related
With 3 levels of abstraction (VS->Mac, Mac->phone/simulator app, app->webview), I'm not sure where to start.
I have cross-plat Xamarin app with nothing more than a webview (in Xamarin.Forms) hosting an external website (I also created). The website & all hosted apps (Windows/Android) perform very well, except on ios-webview. (Safari on ios and phone work fine). However, on ios/hosted-app, a 3 second load takes 60+ seconds.
Hopefully without having to add specific console/debug messages, how do I go about seeing where (in javascript), the time is lost - or what the issue might be?
Thanks,
On a plain vanilla, scaffolded ASP.NET Core MVC web app, with a DbContext registered in the DI container, whenever I hit F5 after 30-60 seconds, I get the error message:
Unable to start program 'http://localhost:60175/'. Operation timed
out.
The home page in an index view, whose action gets all employees from a localhost SQL Server db. The project is already built, so the initial build for debug is quite quick, and doubtfully the cause of the delay.
If I run without debugging, I get the home page up in 30 - 40 seconds.
Just what is timing out, and can I set that timeout? Or is there anything else I can to to speed up this painfully slow debugging setup, compared to MVC 5, where the home page opens after only a few seconds.
It is hard to say if it is the same issue, but I had same symptoms when I was starting my current project. In my case, I found I either had to:
Turn off Browser Link; or
Use a browser other than Chrome as the startup browser.
It wasn't until I selected Microsoft Edge as the browser in the debug button of the toolbar and it worked fine that I realised what it might be, and I disabled Browser Link. It all starts up fine now.
If it is yet another issue, then best of luck.
Since updating to Windows 10, I experience delays (up to a minute) when starting the website I'm developing. The browser opens and it is attempting to fetch the URL but it just sits there spinning until at some point VS kicks back in finally the page loads. This includes new projects since the upgrade to Windows 10 and older projects built before the update to Windows 10. If I make a client side change (ie change some HTML), save the file and then refresh the browser, I also get massive delays. Any ideas?
In addition, during the delay nothing is posted to the output window in VS. The eventual page load coincides with messages appearing in the output window, indicating that the delay is occurring at the VS end.
I work on an asp.net mvc app.
This morning I was able to debug my server side code from a Google Chrome browser instance. I simply select Google Chrome in place of Internet Explorer in my VS2012 then click on it to run the app. When a breakpoint was reached (for example in my controller) it switch automatically to VS2012 for debugging.
This afternoon I am not able to do it again with Google Chrome. Only able to debug with Internet Explorer.
Any idea what's wrong?
It shouldn't matter which browser you tell VS to open your website in. If your debugger is attached to your C# your breakpoints should be hit as long as you're using the correct URI defined by your MVC app. I use fiddler and postman to debug my controllers all the time. Are you sure you didn't make any changes that would cause Chrome to make an incorrect request? Or perhapse the browser has cached old code and that's why the breakpoints are not being hit? I always open Chrome with ctrl + shift N to avoid having any caching issues.
I'm developing an application - something I've done on the same machine for the last x years.
I'm still using XP on this machine - VS 2010. I've also recently changed from the default dev host to IIS 7.5.
At them moment, I'm checking out Google Polymer - this is where the root of my problem lies. When I click on a trivial link to open a dropdown menu, the CPU goes into overdrive and stays there. This only happens on Chrome, not Firefox.
I eliminated a rogue polymer installation by linking direct to the polymer site url's.
I paired the page down so its just html - no aspx.
I put the page up on codepen and I do not get the same issue.
I removed all extensions from Chrome and reset my settings.
I switched betwen IIS and the default dev host.
After these tests, the only variant is that copepen runs the page and I run the page. Therefore my conclusion is that it must be something to do with VS or IIS/dev host.
I'm scratching my head as to where to go next with this. Has anyone else had similar experiences when testing on Chrome?
Help!
Confirmed here : VS 2013 (32bit) + Google Chrome = 100% CPU Windows 8 & 10
You need to diable BrowserLink option in the VS 2013
here is how you can disable it
http://www.asp.net/visual-studio/overview/2013/using-browser-link#disabling
After liasing with the guys from polymer project for sometime, I decided that polymer wasn't ready for production just yet.