I am expierencing a strange problem with Visual Studio 2019. We ware using SOAP-webreferences in our projects. When I start a project in debug mode, the debugger freezes when the SOAP reference is instantiated. Waiting ~5 minutes helps but this problem strongly impaires the development. When I start the same App without the Visual Studio debugger, everything works fine. The bottom line is that I cannot use the debugger right now.
I already tried to set a breakpoint but nothing happens when the debugger freezes - even in the console.
Visual Studio 2019 freezes when instantiating SOAP Webreference
Please try the following steps:
1) disable any third party vs installed extensions under Extensions-->Manage
Extensions to check whether there is an extension causing that.
2) reset all vs settings under Tools-->Import and Export Settings-->Reset all VS settings
3) clean nuget caches first
then run update-package -reinstall under Tools-->Nuget Package Manager-->Package Manager Console
4) close VS, delete .vs hidden folder under the solution folder, bin and obj folder
5) try to use another port under Project Porperties-->Web-->Porject Url https://localhost:<prot>/ like https://localhost:44307/
6) Or try run devenv /safemode on Developer Command Prompt for VS2019 to start a pure VS and then debug your project to test again.
7) If it does not work, you could create a new winform project in VS2019 and then migrate the old content into the new one to test whether the issue still persists. And if it succeeded, it is a better solution to avoid this issue.
If the error also happens on the new one, please repair vs or update vs.
Besides, if these do not work, please share a small sample with us so that it will help us troubleshoot your issue more quickly.
Is this dll not compatible with windows store app, Or is there any other way to achieve the same.
I tried adding it from nuget package also but not happening, I am getting this error:
"Severity Code Description Project File Line Suppression State
Error Package restore failed. Rolling back package changes for 'Solution'."
As far as I'm concerned, you need to intall the Windows Identity Foundation as well as the WIF SDK and then restart the application for the effect to work.
For Windows 10 device, Windows Identity foundation is not an istall but a Windows feature need to be enabled.
Enter Control Panel from Start menu
Click program and features
Choose turn Windows feature on or off
Choose Winodws Identity Framework, click OK
Restart your machine
A similar question here that could be helpful to you. As Moory said in the comment, he fixed this issue by adding the reference below to the csproj file:: ( .
Please also try it. Thank you.
So I just updated to IE10. When I try to debug my web app's javascript, my breakpoints are all just outlines with a little triangle and say in the tooltip:
The breakpoint will not currently be hit. No symbols have been loaded
for this document.
IE10 is started when I start debugging and it goes to the website like IE9 always did. If, in VS 2010, I go to Debug > Attach to Process... and select the iexplore.exe process, as my javascript executes it will hit and stop at breakpoints like it always would with IE9 and everything is peachy until I kill IE10 and start debugging again.
I've made sure that Javascript Debugging is enabled in IE10 and any "solutions" I find online all say to uninstall/reinstall VS2010/IE10 and see if that helps. I already know that VS2010 is capable of debugging, it's just not attaching the debugger properly. How can I fix this so that debugger attaches properly and will hit breakpoints and exhibit the usual behaviour?
Another StackOverflow Post recommends installing VS2012 (any version) and that should fix your issue when debugging JavaScript in IE10 with VS2010.
This may fix JavaScript debugging issue in IE10:
Close Internet Explorer
Press start and type CMD
Run one of these commands in command prompt
32-bit OS
regsvr32.exe "%ProgramFiles(x86)%\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll"
64-bit OS
regsvr32.exe "%ProgramFiles%\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll"
There is another thread on this issue, as Elijah mentions, and this answer is probably more appropriate there, but that thread is closed to me because I'm a new poster. Corey has already mentioned that he can't install VS2012 at this time, but it may be useful to others.
I experienced this same problem after updating to IE10. I already had VS2010 and VS2012 with Update 1 installed, and none of the recommended fixes (including the msdbg2.dll registration) worked for me. What fixed my problem was to reapply Update 1 for VS2012, choosing the "Repair" option. I can now debug javascript in VS2010 again.
Configuration:
Windows 7, 64 bit
Microsoft Visual Studio Professional 2012 RC Version 11.0.50522.1
RCREL
Running VS in administrator mode
The VS solution contains a web
application, with target: .NET Framework 4.
When I press F5, the solution builds... and nothing else happens.
Happens with both IIS or the VS Dev Server.
Happens with Platform Target of "Any CPU" or "x86"
If instead, I use the Debug / Attach to Process... menu, after a few seconds, I get:
"Debugger is Busy" - Debugger is performing a remote operation that is taking longer than expected. This dialog stay until I click "Terminate" and confirm it.
Then this dialog appears:
"Microsoft Visual Studio"
"Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named [COMPUTER NAME]. The network connection to the Visual Studio Remote Debugger has been closed."
After clicking OK, the 'normal' "Attach to Process" window finally shows up. In it, the list of "Available Processes" is empty.
Any suggestions or clues?
The main points that I wonder about:
Why is the list of processes empty? It is not surprising that the debugger does not work if it cannot see any processes.
Why is it trying to do "remote" debugging, when it is just accessing the local computer?
(Cross posted on social.msdn)
I had the same problem in VS 2012 (not the RC, but the final release) using a VS 2010 project. It would build fine, but the debugger would not start. So, I modified the solution file:
Changed "Format Verion 11.00" to "Format Verion 12.00"
And changed "# Visual Studio 2010" to "# Visual Studio 2012"
It's a workaround for now until my company upgrades its projects to VS 2012.
I've got a similar setup and I'd followed all the suggestions here and on Microsoft Connect - none of which worked for me. The only thing that did work was renaming MSVSMON.EXE in the x64 folder to MSVSMON.EXE.OLD and copying in the file from the x86 folder in it's place. I'm not sure if there are any other implications in doing this but it seems to have solved the problem in my case.
I eventually resolved this problem by deleting the msvsmon*.* entries in the \Windows\Prefetch folder. After doing so I could debug normally.
Ultimately, a Repair of the VS2012 resolved this issue for me. I followed the advice found at your social.msdn cross-post without any resolution (Devenv.exe /SafeMode /ResetSettings /ResetSkipPkgs and /Setup). Like you, my solution (VS 2010 SP1) also has a web application (targeting .NET 3.5), and the startup project is set to a winforms app. The ASP.NET development server did not start, nor did the app I was trying to debug.
Note that this issue was also posted to Connect at this link (by you?). If anyone else sees this issue, the Connect folks are requesting running the Microsoft Visual Studio 2012 Feedback Tool to collect data. As I started the Repair process prior to finding the Connect issue, I did not and was not able to provide feedback to MS with logging.
Seen a similar issue when running both Visual Studio 2010 and Visual Studio 2012 at the same time. Closing Visual Studio 2010 allow the debugger to start working in Visual Studio 2012.
I had the same issue - starting debugger just told me what a good job it had made of the build and the decided that that was enough.
I feared the worst, but luckily for me a reboot fixed the problem.
I know that this is therefore a pretty useless post in as far as offering help to anyone suffering with this issue, but I thought it was worth noting the point as it shows a) another person with the same problem so please fix it MS, and b) that sometimes a reboot fixes it so maybe that tells the maintainers something.
If you are opening a VS 2010 project with the new VS 2012 version it's probably your bin and obj folders that are causing the problem,deleting them solved the problem for me.Or you could clean your solution but I preferred manual deletion.
I just closed and reopened VS. This seemed to fix my problem
On another computer, with the RTM of Visual Studio 2012, I opened an older project and found that I could not press F5 to start the application. All that seemed to happen was a message in the status bar on the bottom edge of the window: "This item does not support previewing".
This solution had two projects, and the correct one was bold in the Solution Explorer, presumably indicating that it was the startup project.
However, after selecting the project and choosing "Set as Startup Project" in the context menu, I was then able to use F5 to run and debug it.
It turns out that the "This item does not support previewing" was nothing to do with the problem, but is a message that shows on the status bar whenever the item just selected in the Solution Explorer does does not support previewing.
For what it's worth, I found that I received this error message when I had an entry missing in my hosts file. I am using local domain aliases and the one I was trying to debug with wasn't in hosts. Adding the missing entry solved the problem for me.
Just copy all dte*.olb files, from C:\Program Files (X86)\Common
Files\Microsoft Shared\MSEnv to C:\Program Files X86\Microsoft Visual
Studio 9.0\Common7\IDE.
From https://mycodepad.wordpress.com/2013/12/07/visual-studio-2012-4-run-as-administrator-the-application-cannot-start-error/
Just my two cents,
I have experienced this issue twice now and it turns out after all of the suggestions I tried, it was BitDefender on my local machine that was doing this. So my fix for this problem is to try adding in exceptions to the local security software into the firewall and AV parts of it. Tell it to ignore the msvsmon.exe and devenv.exe altogether and see what difference that makes.
Otherwise try ripping it off altogether and see if the it lets you debug your solution.
You can see here for more info: http://forum.bitdefender.com/index.php?showtopic=37028
I installed the latest BitDefender version and all was fine for me.
I personally encountered some comparable problem: Visual Studio 2010 did not begin debugging but froze.
When I clicked VS it displayed a "Wait some more" or "Switch to" message box which didn't help me.
Using a task manager I could kill the *.vshost.exe process which brought VS back to life but aborted the debugging. Launching the program without debugging started the application instantly.
Solution:
Disable the indexing service for your code directories! Either deactivate the index service or uncheck the folders in the Indexing Service control panel.
Had this problem for a C++ application. Looking at the devenv.exe events in ProcMon pointed me to it trying to load a Visual Assist configuration file, which I had in my disk cleanup zeal accidentally deleted. Removing and then installing the extension again fixed it for me.
I have fixed the same issue by checking off the "Enable the Visual Studio hosting process" option from the start-up project Properties->Debug - Enable Debuggers options
All you have to do to fix this is go "Project > Set as StartUp Project" then hit F5 or the debug button and it will work!!!
I had VS2010 running fine with Silverlight development. Then I installed Expression Blend 4. Now when I run VS2010 and try to debug a silverlight app I get an error saying "Unable to start debugging. The silverlight developer runtime is not installed. Please install a matching version." I've tried uninstalling silverlight tools, and reinstalling them from scratch (the latest april version). But I still get the same message. So basically I'm now unable to do VS2010 SL development. I'm on the verge of just rolling back to my last system restore point and giving up on Blend. But if I do that I'd be worried that Product Activation would never allow me to reinstall it in the future, since the MSDN download page implies I'm only ever allowed to install it on a single machine. Any help appreciated.
Thanks
I had the same problem after installing Expression Studio 4. I installed the Developer version of Silverlight at: http://go.microsoft.com/fwlink/?LinkID=188039
and the problem seems to be resolved.
Hope that helps.
Try reinstalling or reparing the Silverlight_Tools for Silverlight 4.
You tried that.
The product activation system isn't that draconian it has to allow for things like hardware failures etc which would require re-installs.
Thanks for the suggestions. I solved it this way: Since I'm running under parallels, I rolled back to a snapshot taken before I'd installed Blend. Then I rebooted Windows. Then I reinstalled Blend (happily with no draconian activation problems!), and everything worked.
So why did it work the second time and not the first time? The first time I installed Blend, I'd shut down VS2010, explorer etc, but not rebooted. Perhaps some hidden VS-related process was still running. Installing Blend in that situation screwed everything up, and removing and reinstalling stuff didn't fix it. Obviously the Blend installer should have spotted the dangerous process and taken remedial action, but it didn't. Perhaps MS recommends you reboot before installing new software? That would be a bit of a nuisance, and I've never needed to before. My real lesson from this is to work in a VM and take regular snapshots.
Thanks again.