Visual Studio 2010 Extension - Cannot break execution in Experimental Instance - c#

I am trying to break execution with Debug points in a Visual Studio extension running against a Visual Studio 2010 Experimental Instance.
For some reason, when trying to break execution, I receive an error:
"Unable to break execution. This process is not currently executing the type of code that you selected to debug."
Oddly enough, I can debug without any problem in a Visual Studio 2005, and 2008 Experimental Instance.
Has anyone else ran into this with VS 2010?

It sounds like the problem is that you're setup to debug only managed code in your VS 2010 project file. If you're setup to debug only managed you'll get this message if VS is currently executing native code (VS spends a good portion of it's time in native code).
To fix this do the following
Right Click on the project and select Properties
Go to the Debug Tab
Check "Enable unmanaged code debugging"

I re-installed Visual Studio 2010 and the SDK. This seemed to work at first, but after changing a source file and launching the Debugger, I was unable to break execution yet again.
I went to Tools->Options and unchecked 'Only build startup projects and dependencies on Run'. This fixed it! This must have something to do with an extension solution that supports both VS2008 and VS2010.

Related

Add debug symbols for .NET 3.5 Debugging in Visual Studio 2013

I have a Unity application and a C# DLL, created by Visual Studio 2013, that I want to debug. I do this by going to DEBUG > Attach to Process inside Visual Studio 2013, and if I choose Native code, I can set breakpoints for C++ code and etc. However, when I choose the option for .NET 3.5, it says that the breakpoint will never be reached as the symbols have not been loaded.
How do I load debug symbols for .NET 3.5 for Visual Studio 2013?
Please have a look at the below MSDN links
https://learn.microsoft.com/en-us/visualstudio/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger?view=vs-2017
https://learn.microsoft.com/en-us/visualstudio/debugger/how-to-debug-dotnet-framework-source?view=vs-2017
You can load the symbols from pdf file and making configurations in pdb file you can manage the symbols while debugging the application.
Ok,
The answer is simple, you have a dll, debug symbols are .pdb files. You need to open and build c# solution (class library) in visual studio and look in the output directory of the project, usualy bin->debug. Get the pdb and store them somewhere. Then when you run your unity applicatio, you use visual studio (can be any version of visual doesnt matter), attach to process, but make sure the pdb's you saved have been loaded into visual studio by following the microsoft documentation above.
If you don't have the library's symbols file, you can decompile the library with the free decompiler dotPeek and attach Visual Studio to the dotPeek's symbols server.
Then disable Enable Just My Code in Visual Studio's debugging option. Remember to enable it again, when you're done, because it hurts the performance.

Is it possible to debug compiled .NET or C# with Visual Studio Code?

I have a an application that is using .NET framework 4.0.0.0. I don't have Visual Studio installed, at the moment nor do I have the source code for this application. I would like to debug it to find out why a specific feature of the application is failing. With Visual Studio, I could potentially attach the process and debug.
Instead, I installed Visual Studio Code. Is it possible to debug a .NET application with Visual Studio Code without having access to the source code? I read elsewhere that, for Visual Studio, if you have the PDB, you can do some debugging:
how to debug anything with visual studio and jetbrains dotpeek v1.2
With dotPeek, you can start a symbol server and then have Visual Studio leverage that server, acting as the PDB file.
I do have JetBrains dotPeek v1.2 installed.
If I can't debug compiled code straight with Visual Studio Code and since I don't have the PDB, would it be possible to use dotPeek and Visual Studio Code, in concert? And, if so, how would I configure it?
Thank you kindly.

Visual Studio only any cpu debug .exe works

In Visual Studio 2015 community when building forms-applications, only when configuration is set to "Debug" and platform to "Any CPU", the generated .exe actually works. ANY OTHER configuration just doesn't run.
If I try to delete the bin-folder it says the folder is used by another program. Still nothing shows on task manager. I have to reboot to terminate it.
This happens even on empty projects so it can't be caused by my horrible coding. I've even reinstalled Visual Studio but no luck.
I need this to work for my installer that doesn't work with "Any CPU"-config.
So how do I get all configurations to work?
Thanks for helping!

Visual Studio won't load my VSIX package

I'm trying to create my own VSIX package using the Project template. But when I actually launch it, it doesn't appear to be loading anything. That is, when running the project, it opens up another copy of visual studio, but it doesn't actually load up my plugin. I've compared my plugin to the other sample templates, and I just don't see anything wrong. It seems like it should be pretty straightforward. Are there any other steps besides creating the project that I have to do?
Are you using the visual studio experimental instance for debugging? You can enable this in the Project properties (right click your project and choose properties). Go to the 'Debug' tab and add the following line to 'Command line arguments': /rootsuffix Exp
More information about the experimental instance can be found on msdn.
I spent an entire day trying to reset Visual Studio (2015 Community Edition) by unloading features, deleting the cache directory, using the install to repair -- all with no success.
I finally uninstalled Visual Studio with success. When I initially installed Visual Studio, I had packages errors, like Python, that failed to load, but my Test Explorer worked beautifully. The test Explorer package stopped working in time. After re-installation, everything worked without any package load errors. Also, pay attention to the xml error files, because mine produced exceptions thrown by the package. (The xml error file is reported in the error dialog when Visual Studio informs the package failed to load.

Visual Studio 2008, excel add-in hangs when stepping in debugger

I have a background worker in my C# vsto excel add-in that reads data from an excel sheet. Recently, and for no apparent reason, Visual Studio hasn't been stepping through the background worker code correctly.
I have Visual Studio set to break on all exceptions. Previously, when an exception occurred or I hit a breakpoint, Visual Studio would break and I could step (F10) through my code, as normal. Now however, when Visual Studio breaks I can sometimes step once or twice, but then the background worker/excel will suddenly hang (Sometimes Visual Studio hangs too). If I pause execution and look at threads, I can see that none of them are in my code anymore.
I've tried this hotfix, but it hasn't helped.
Has anyone encountered this before?
Additional Info: I've used git to roll back to a version from before I was experiencing this issue, and it is now present in that version as well. This leads me to suspect it's something specific to visual studio.
The solution, from MSDN's Amanda Zhu, was to restore Visual Studio's default settings.
Navigate to \Common7\IDE (default is C:\Program Files \Microsoft Visual Studio 9.0\Common7\IDE);
and run:
Devenv.exe /ResetSettings: Restores the IDE's default settings, optionally resets to the specified VSSettings file.

Categories

Resources