I have an ASP.Net Web Site with GridView control that in turn contains a ButtonField column. It's supposed to do a postback when this ButtonField is clicked, but that doesn't happen if I click on the button from within the Internet Explorer window that Visual Studio opens while debugging. I can get it to successfully postback when I bring up and click on the ButtonField from an externally-invoked Internet Explorer window or a Firefox window, but never from the window Visual Studio produces.
I'm using:
Windows Vista Home Premium
Visual Studio 2008, running as Administrator
Internet Explorer 7.0.6000.16809
Firefox 3.0.6
Do you have any javascript added to that button? If javascript fails onclick it could bring up the debugger when running via VS but any other browser might just be eating the error.
I've determined the problem is due to running Visual Studio 2008 as Administrator under Windows Vista. Doing so causes some kind of issue with Javascript that prevents GridView ButtonFields from issuing postbacks. Contrary to Microsoft's advice for the previous version of Visual Studio (2005), debugging with Visual Studio 2008 running under Windows Vista requires that the IDE not be run using "Run as Administrator".
Related
I'm pulling my hair out over this since I'm already searching for a solution on it for a few days.
The problem is that when no instance of Chrome is currently opened and I press the Google Chrome Button to launch my web application, Chrome opens a new window on a gray screen. I can't load any pages, not even the settings page. It only occures when I do it from Visual Studio in Administrator mode. When an active instance of chrome is already opened, it will successfully open on that instance in a new tab. When I open the Chrome exe in the program files or via my desktop shortcut, it also works fine. It seems to only occur when launched from within VS administrator modus.
Steps to reproduce in my case:
Open VS in Administrator
Close all instances of Chrome
Launch web application in Chrome
New Chrome window opens with unresponsive gray screen:
Screenshot of the result
I've already tried:
Repairing VS
Reinstalling Chrome
Anyone already encountered this problem and has a solution?
Cheers
I had the same issue for a day or so and was really getting on my nerves!
I tried a few things:
Loading Chrome in Administrator mode (didn't work)
Loading Chrome independently, i.e. not getting Visual Studio to debug directly in Chrome, then pointing it to my app (didn't work)
Setting Chrome to always run in Admin mode (didn't work)
Finally I set Chrome's Compatibility settings to run Windows 8 and it seems to work now! Even from VS firing it directly into Debug mode.
I'm running
Windows Server 2012 R2
Visual Studio 2015 Pro
It's worth noting this issue NEVER happened in Visual Studio 2013 Community.
Hope that helps
Chrome compatibility settings
when i debug my ASP.NET application / website in visual studio , after closing browser window ,debugging not stop and IIS Express Still working.
how can i stop debugging after close browser
i am develop my program in visual studio 2012 SP1
Closing the browser window in Visual Studio 2012 will detach the debugger. If the ASP.NET development [web] server is still running after you do that, you can always right click on it in the system tray and select "stop".
i have designed a web page in asp.net and vs 2008.
In this web application i have a from which pop up the crystal reports window .When i run the application through Visual studio 2008 and browse it in any browser it works fine.
But when i deploy the application on my local computer through iis 7 the toolbar of crystal report is missing in firefox only but working Perfectly in Internet explorer and Chrome.
Can any one tell what changes i have to done i am googling this from yesterday but not found the soultion.
Plz help me !!!!.
C:\inetpub\wwwroot\aspnet_client\system_web\2_0_50727 in this path copy the folder
CrystalReportWebFormViewer4 and place it in
C:\Windows\Microsoft.NET\Framework\v2.0.50727\ASP.NETClientFiles then tool bar will come.
Has anyone else run into this problem and resolved it?
I am developing with Visual Studio 2010 in a clean install of RTM of Windows 8. While developing an ASP.NET application and RUNNING it with the Debugger Attached, I can not click on HTML links in ANY application and have it open up a browser window.
I will be running(debugging through VS) my application in Firefox, and I can't click on links sent in Google Talk or Outlook.
If I stop the application from running, I can then click on those links.
I have also seen that while debugging, I am using jQuery Drag-N-Drop HTML 5 functionality in my application. I can't use that functionality while it is running under the debugger, it just doesn't work. This happens with all browsers (Chrome, Firefox and IE). But if I stop debugging, and run it without the debugger on, it then works.
Any ideas?
Try to disable the debuging for "Javascript" in Visual Studio 2012.
I'm developing an ASP.NET MVC 4 site using Visual Studio 2012 Premium on Windows 8 RTM x64. When I right click on the web application and choose Publish, Visual Studio 2012 returns the message:
"fail to open url of 'http://.../'.
Exception:Class not registered"
The publish process seems to work correctly but it fails to launch the browser. This happens every time I try to Publish the site and it happens with Chrome (21.0.1180.79 m) or Firefox (14.0.1).
Furthermore, since the site isn't launching post Publish, I do it manually using Ctrl-F5. I'm able to navigate around the site normally, but if I right click on the browser's icon on the task bar to launch another browser instance, nothing happens. Once I close all browser instances, the browser task bar icon reverts to its normal behavior.
I'm not sure if these two issues are related, but the common theme here is launching a browser from Visual Studio 2012 causes unexpected side effects. The browser either fails to launch on Publish or launches with Ctrl-F5 but renders launching another instance useless using the task bar icon.
Any help is appreciated.
EDIT: I've re-installed the entire software stack (Windows 8, Office 2010, Visual Studio 2012, Windows Update, Chrome, Firefox). The above issues continue, unless I make Internet Explorer the default browser.
Thanks.
I filed a Chrome bug, it was a browser registration thing. If you uninstall and reinstall from a Download and be SURE to say Yes to the UAC prompt, Chrome will register Machine Wide, rather than User. That is required to launch as Admin. (HKLM vs. HKCU)
It appears this problem is much more widespread than the Web Publish operation. Anytime you use the ShellExecute() API (or Process.Start) to access a URL it fails when running under elevated rights (ie. Run As Administrator).
I see this in any application that uses Process.Start() or ShellExecute(). When UAC is on and I run it normally under the UAC account everything works and the browser opens. Run with "Run As Administrator" it fails. It's easy to test.
Not sure if this is a bug in the OS, or whether Microsoft deems this as a security 'feature'.
FWIW, some people have mentioned the setting IE as the default browser works, but it doesn't work for me. Basically no links work if I've elevated rights. This has actually broken quite a few administrative applications we use in the back office for administration.