Not sure if this is the right place to ask this question, but I am seeing an annoying issue when debugging ASP MVC applications on visual studio.
After pressing F5, Firefox opens and everything works normally, but after doing this a few times, when I try searching anything on google from the same network I am presented with multiple captchas (usually 2 at a time).
It seems that Google thinks there is some suspicious activity going on on my computer, but of course everything is just fine.
I am still able to search normally through Chrome, IE etc.
Has anyone else expereienced this issue? If so is there perhaps an option within VS or in my browser to prevent this from happening?
Related
I am working on Google Cloud Platform to develop a project in API.AI, I have an integration (in API.AI) with Google Actions (for Google Home or Google Assistant), they provide me to see my progress as real time in web-simulator, that you can find here:
https://developers.google.com/actions/tools/web-simulator
I am trying to START the web-simulator clicking on START button, then I get a window pop-up but after open, it closes, I try and try again but I obtain the same result, I cannot open the web-simulator. I have allowed the popup windows in my browser.
Of course I have completed all steps to start web-simulator...
I don't know what is happening. Someone can help me? Thank you, have a good day.
First, are you using a compatible browser? Try it in Chrome if you're
not already using it, as Chrome is a Google product, and so is the
web simulator.
Next, are you using any Ad-Blockers or
Script-Blockers like NoScript? If so, try disabling them, as they
could interfere with the operation of the tool.
If it still doesn't work, try going to an Incognito Windows by pressing the
three dots button and opening a New Incognito Window. Go to the page, and log
in. This will ensure that no cookies are interfering.
At this point, if you're still having issues, try a different browser.
(Either Firefox or Opera)
I'm posting this with the hope to find an active Firefox developer to help troubleshoot a nasty bug. When using the Firefox browser with my web application, the page sticks within the tab and doesn't want to change. Clicking links to navigate off the page or just changing the address in the bar doesn't leave the page. This only happens in Firefox. Here's a screencast of the issue.
http://screencast.com/t/Xr662nAr
I can give a developer access (private message) to the application to help troubleshoot this issue. At the moment, we have to tell our clients to stay away from the Firefox browser when using our application or deal with this issue until it is resolved. We have no such problems with Chrome. So far I've been able to replicate this on both windows and linux.
Thanks!
I have a web application that uses IIS, but when I try to debug it VS just locks up and gives me the hour glass cursor icon. No browser window opens, nor does an instance pop up in the Task Manager. VS says its Running / not "Not Responding", but I cannot interact with the IDE. Can't Ctrl-Break to stop or anything.
I was able to run it before, and I'm not aware of any system or IIS changes that could cause this. I've disabled source control and I've tried launching the app in both Chrome and IE but it still behaves the exact same way as described above.
Has anyone else encountered this? The only threads I could find just describe general slowness in the IDE but otherwise its functional. The recommended fix was to disable the source control functionality, which as I said I already tried.
I should note that I don't seem to have an issue running & debugging winforms applications. I also just created a web application and was able to launch it in Chrome and get to the homepage. Also, it doesn't make a difference if I have a breakpoint set or not.
This solution has 4 different projects. If I set a different project as the Startup Project, it does run and launches the browser but it just gives me a 'file explorer' sort of view where it just lists the files in that project's directly which is obviously not what I want.
Edit; If I manually open a browser tab, try to navigate to http://localhost/myApplication, VS pops up and asks if I want to attach process w3wp.exe to IIS APPPOOL\myAppPool. If I attach, it opens a new tab in Chrome and my application runs. But unless I do these 2 steps, it does not run.
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've got this weird bug. The progress bar in IE's bottom-window status bar keeps incrementing very slowly after an Ajax POST. At least that's where I think the problem is.
How can I tell what the hell IE is doing that's causing the progress bar to keep going? In FireFox, I would just look at the Console tab in FireBug and see what's up.
I turned Fiddler on but it doesn't pick up any HTTP requests or responses being sent.
What can I do in IE?
I'm not very experienced in Web debugging but you might try the Developer Tools that come in Internet Explorer 8. It's under the Tools menu, or just hit F12. I think the Profiler tab may be helpful. I had heard somewhere that the IE8 Tools were created to mimic Firebug's feature set as closely as possible.
An another tool for checking HTTP requests is the Debugbar
This might not help if Fiddler isn't picking anything up, but HttpWatch is a great http request debugging tool for IE.
I don't think there is a problem here, earnestly. IE has a bug where it shows that a request has not yet been completed when it has. This has been around for a while now, and I have tested my own applications against it. There is nothing happening and there are no connections waiting for a response, yet the browser still thinks there is an open connection.
i recently discovered this tool for earlier IE versions which can be used in combination with the IE debugger for network profiling and more behind the scenes debugging
http://www.ieinspector.com/httpanalyzer/
open IE ...thn press F12 ...here you will get many menus..to debug script choose "SCRIPT" option..and start debug...and if there is any error on page...thn u will get on Console option..also see on attach image...