when i push F5 in a VS2005 web service project,
a new explorer window opens and the Web service i try to debug opens.
but the VS2005 doesn't stay attached to the new window. it just stays like i didn't run the service.
when i use the service in the new window that opened , the breakpoints in the project doesn't work.
its like ,when i pushed F5 i opened a new process that is notattached to my project
(using "Attach to Process" doesn't solve the problem).
it worked before but now it doesn't...
the project and the service page are both "Set as Startup Project/Page".
I found the problem. it is The windows Explorer 8!
The windows explorer 8 doesn't let two projects of VS2005 be debugged together.
i had two VS2005 projects that one is the simulator of the other.
i needed both applications to run together - each project that runs (and debugged) opens a different Explorer window. The problem was that when one project opened, the other couldn't be attached to its window.
uninstall windwos explorer 8 and roll back to 7 version of explorer. it solves the problem!
Related
At some point today, whenever I run the C# console app that I'm developing in Visual Studio 2022 on Mac, a pink/purple window opens with the title "TerminalPad-TerminalPad-0" in the frame of the window. An additional normal looking terminal window within which the application actually runs opens, takes keyboard input and displays output. When the application successfully completes, the pink/purple window goes away.
How do I stop this purple/pink window from opening?
I tried changing all the terminal options I could find in VS with no change. I don't know what I did to make this start happening.
I started having this happen to me today (11/10/22) as well. There's another thread with the same issue, required a full uninstall with a 3rd party uninstaller ("App Cleaner and Uninstaller", has two day trial) and then full reinstall. Just dragging the Visual Studio icon to the trash won't fix it.
I had this issue after a VS update. I uninstalled using the Microsoft provided scripts linked to from within this page:
https://learn.microsoft.com/en-us/visualstudio/mac/uninstall?view=vsmac-2022
and currently leading to the script at this location (please double check above page if the below link is dead):
https://raw.githubusercontent.com/MicrosoftDocs/visualstudio-docs/master/mac/resources/uninstall-vsmac.sh
I then reinstalled using the MS provided installer for MacOS. All working fine now.
It took around 15 mins in total to resolve.
New install of VS 2013 Pro, Windows 8
Creating a new win32 console project appears to work - but after it gets done creating the project, the create project dialog opens again. If I try to continue with that, I have to give that project a different name to create it. Then the dialog opens again. Repeats indefinitely.
If I click "cancel" instead of "create" to get out of the loop, the application stops working.
Repairing the installation and a reboot (may not be required) fixed this for me in Windows 7.
I am using Windows Remote Desktop (RDP) to connect to my office computer via a Cisco Gateway. In VS2012, my project is open and I clicked Build/Publish Web menu. The Publish Web wizard window flashed for a second then disappeared. It seems to go behind the main VS2012 and made the main VS2012 go into modal mode. It does not respond to any mouse or keyboard commands. I had to use Task Manager to kill it then relaunch it to regain control. This doesn't happen when I am in front of my office computer. I can see the Publish Wizard in front of the main VS2012 window. This doesn't happen to my coworkers who are also telecommuting via RDP. I tried to look up VS2012 log, but there is no such a log file on my computer. Windows Application Log doesn't say too much either. There are 2 devenv.exe *32 in the Task Manager Processes tab. I killed the one with smaller memory size. It still wouldn't make the main VS2012 come out of modal mode. Please help. Thanks.
I can no longer debug my Silverlight application in Visual Studio after updating to Internet Explorer 10. I made no other changes to my system and it was working fine with Internet Explorer 9 just before the update to IE10. When I hit F5 in Visual Studio, IE10 is fired up and the Silverlight application runs in the browser, but breakpoints are not hit in Silverlight code. If I hit shift+F5 (stop debugging), the browser remains open (this used to shut it down). Alternatively, if I close the browser while debugging, it doesn't stop debugging in Visual Studio (which it always did before). I'm running Win7 64.
This problem has also been reproduced in Visual Studio 2010 and Silverlight 4.
I had the same problem with Visual Studio 2012 and Silverlight 5. The symptoms that I was getting included the following.
Multiple browser instances would be opened when I started the application in debug mode within Visual Studio.
I sometimes got an error in the browser saying that the application could not be loaded.
Visual Studio would automatically detach from the browser and drop out of debug mode.
Turning off the Silverlight debugger (see the Web tab in the properties dialog for the web project) seemed to result in less of the other problems. This did however mean that I could not debug Silverlight code.
To resolve these issues, I right clicked on an aspx file in the solution explorer and selected 'Browse With...' to open the following dialog.
Note that there are two entries for 'Internet Explorer'.
I removed both (I set Firefox as the default temporarily to do so), cancelled out of the dialog and then reopened it. At this point, a new entry for 'Internet Explorer' had been added back in automatically. I made this the default and then had no further issues.
I had the same with VS2012..
Looks like Visual studio got confused which IE to use - somehow in system I hade two instances of IE as target browser (In VS2012 window called "Browse With..")
I removed all IE's from VS targets and restarted VS. Then only one instance of IE appeared after and debugger attaches normally.
I had a similar problem after opening a Silverlight-based application in two instances of IE10 at the same time. I could not debug. After which, I had switched between Chrome and IE10 in order to try and solve the problem. I could debug in Chrome but not IE10. But Chrome was cumbersome to run for debugging purposes.
Ultimately, I had to remove all the temporary files associated with VS builds in a three places:
C:\Users\brchase\AppData\Local
C:\Windows\Microsoft.NET\Framework\v4.0.30319
C:\Windows\Microsoft.NET\Framework64\v4.0.30319
As well, I had to do a complete clean on the project and shut down IISExpress.
Also, I did a Tools /Delete Browsing History in IE10.
The above worked and I could debug again in IE10 -- even with multiple instances running.
Using Winserver 2008R2, VS2012 or VS2010. Latest version of FireFox does not hit SilverLight breakpoints. Tim Heurs solution at http://timheuer.com/blog/archive/2010/08/16/enable-silverlight-debugging-in-firefox-visual-studio.aspx does not apply as the required line is not in the FireFox config. My fix was to go back to IE9 (My IE10 was broken so I can't say for sure IE10 doesn't work)
Tried all of these suggestions.
Finally had to remove and re-install VS 2012 (which isn't straight forward anymore because after Oct 2013 some of the certificates had expired). Yay Microsoft!
So after re-installing I still had to go into the "Browse To" and switch it from IE to another choice then back to IE and it magically works now..
I think it was because Internet Explorer updated itself and left VS confused..
First of all, everything was working fine for several months:
When I tried to debug a web app with Visual Studio 2005 and Internet Explorer 7, I just click "Start Debugging", a IE window opened and the process was attached to the debugger.
But after I installed IE 8, the process was not attached automatically. I had to attach manually to be able to debug anything.
Then I discovered that to make it work correctly I had to close all other instances of IE 8 before start to debug. But I did not need to do this with IE 7.
I have Windows Vista Enterprise and everything is up to date.
Is this the correct behavior? If it is not, what I have to do to debug a web app without having to close any other IE 8 instances?
The problem is caused by IE8 creating new processes for each new tab.
This is the solution
1) Open RegEdit
2) Browse to HKEY_LOCALMACHINE -> SOFTWARE -> Microsoft -> Internet Explorer -> Main
3) Add a dword under this key called TabProcGrowth
4) Set TabProcGrowth to 0
Check out this link for the full details from Brad Sullivan
http://social.microsoft.com/Forums/en-US/vsdebug/thread/e2c795cd-b7a0-4fad-b7c9-b1ca40d7302e
In summary: IE8 creates a new process for each tab. The VS2005 debugger doesn't know which process to attach to, and so doesn't attach to anything. The solution is to stop IE8 creating new process for each tab. Brad mentions that this problem is found on older versions of the VS debugger, but does not say if it works properly in VS2008 or VS2010.
Edit: If you are using Vista you need to turn off IE "Protected Mode" which is a checkbox on the Security Tab under Tools -> Internet Options.