I am getting the following error in Visual Studio 2013 every so often when debugging. This didnt happen in Visual Studio 2012.
It seems the default settings in VS2013 changed slightly (from what I can tell anyway). Go into Tools -> Options -> Debugging -> General. Scroll down and uncheck "Warn if no symbols on launch (Native only)". That should stop the message from appearing.
Related
I have a project that is working correctly on Visual studio 2013 Ultimate.
Now we have installed Visual studio 2017 Enterprise.
When I compile and run my project on VS2017 , on several lines of code I receive a strange error message :
"Cannot obtain value of the local variable or argument because it is not
available at this instruction pointer, possibly because it has been optimized away."
What can I do , because on VS2013 I had no problems at all.
Thank you !
uncheck in the project "optimize code"
Also, set the debug info dropdown to full in the advanced options
go to Debug->Options or Tools->Options
and check Debugging->General->Suppress JIT optimization on module load (Managed only)
if you would like a technical reason, you need to post your code
I updated to Visual Studio 2015 Update 1 RC since I want to be on-the-edge with the XAML Designer.
When I stop debugging or an exception occurs in a Windows Phone 8.1 App, I crash every time and my only solution is to restart visual studio..
My solution: For now I rollback-ed to Visual Studio 2015.
Anyone knows why?
I've figured that this crash happens when the solution contains a WPF project (which doesn't needs to be the start project or to be started at all) and the XAML UI debuggintools are enabled.
Going to tools -> options -> debugging and unchecking xaml ui debuggingtools stopped the crashes for me.
Whenever I click "Attach to Process..." in the Visual Studio 2013 Visual studio crashes on me before seeing the attach dialog, regardless of if I have a project loaded or not. I can click debug and get into debug mode but I really need to attach.
Things I've Tried:
Uninstalled and Reinstalled VS
Loading Visual Studio with "/safemode"
Loading Visual Studio with "/log" and checking the log (no notable errors listed)
Deleting my Local Temp folder
Additional Info:
OS: Windows 8
Version: Visual Studio 2013 Update 4
Exeption when debugging VS crash:
An unhandled exception of type 'System.AccessViolationException' occurred in Microsoft.VisualStudio.CommonIDE.dll
Not sure what else to try or where else to look, I have VS 2015 preview install and it has no problems.
In my case the culprit was "PowerShell tools for Visual Studio 2013". I disabled it and the problem disappeared.
Tools => Extensions and Updates... => choose the extension and press Disable
Does anyone know what extension causes this whenever you remove a project from a solution in Visual Studio 2010?
Microsoft Visual Studio
Visual Studio has encountered an unexpected error.
OK
I've been having this problem for a while.
I have installed four extensions from the Online Gallery:
I Hate #Regions v1.2.6
Productivity Power Tools v10.0.20626.18
Visual Studio Background Customizer v1.0
Visual Studio Color Theme Editor v1.3
For me, the offending extension is Productivity Power Tools.
I have just confirmed this by turning off all of my extensions, then enabling one (and only one) at a time, removing a project from a solution, and then attempting to save the solution.
With Productivity Power Tools as the only enabled extension, I received the "Visual Studio has encountered an unexpected error" message.
Hope this helps.
In visual studio 2008 while in the debug mode when we initiate a thread and put break points inside the thread function. Visual Studio doesn't debug giving explanation that i don't have the code. Why does this happens. How to do it
Try unchecking the Just My Code option in Tools -> Options -> Debugging.