Problem description:
Whenever an exception is thrown and not catched a dialog pops up. I want Visual Studio Express 2012 just to break and stop grabbing all my input with this modal dialog window. Example of the dialog:
Wanted solution:
VS 2010 does not show this annoying pop-up window but something called exception assistant. How an I can get the same type of break on exceptions in 2012 as in 2010? Even if that's not possible I really want the pop-up to be gone while keeping the break.
Things I've tried to solve this problem:
Search for a solution on both Google and here on StackOverflow (some of the keywords I used: visual studio 2012, pop-up, window, dialog, exception assistant, exception, break)
Run repair on VS 2012
Uninstall and delete settings (folder: C:\Users\<username>\Documents\Visual Studio 2012) followed by an install
Tools -> Import and Export Settings -> "Reset all settings"
Enable the "Break when exception type is thrown"
Change settings in the: "Tools -> Options -> Debugging -> General"
Edit:
I'm using the Express edition, no exception assistant anymore! :(
Edit2:
Found a (very ugly) workaround using AutoHotkey:
#SingleInstance force
#Persistent
loop
{
WinWaitActive, Microsoft Visual Studio Express 2012 for Windows Desktop
WinClose, Microsoft Visual Studio Express 2012 for Windows Desktop
}
return
Based off of answers on the following forum, VS 2012 Express no longer has the exception assistant option:
http://connect.microsoft.com/VisualStudio/feedback/details/762652/enable-exception-assistant-option-missing-from-vs2012-express-for-desktop
Hopefully we'll see it back in future versions of VS Express. VS 2010 Express is still available to my knowledge, and 2012 can read 2010 projects without destroying compatibility. So if it's a big deal to you, you can go back to 2010 to trace the bugs. Not a particularly exciting solution, but I'm still impressed that Microsoft has given out as many features as they have in the Express editions.
In VS2012, when I unchecked Tools -> Options ->Debugging -> General -> "Enable Exception Assistant" I get the annoying dialog box.
Related
On Visual Studio 2022, Windows 11.
Linq to SQL tools is installed from installer (Individual Components).
When right clicking a dbml file and View Designer, it just sticks on this and eventually needs an end task:
Tried (to no avail):
Clearing all app.config connection strings in the same project (in case it was silently barfing on one of those)
Installing older .NET frameworks, ticking on Data Storage and Processing and Data sources and service references
Any ideas what might be causing this? (Ran OK under Win 10 / VS 2022).
Edit: I've had this after every new PC install with Win 11, VS 2022 (3 work PCs), but it seems to resolve itself after a few days. I now know why, see marked answer re toolbox.
I experienced the same problem on Win8 with VS 2015 and 2017 and 2019, Win10 with VS 2015 and 2017. I did not solve the problem. Do not know what causes this problem. But now on Win11 with 2022 I opened my problematic DBML file, it took really long time to open (during opening it showed Not responding etc.) but finally VS opened DBML file. Then I made a change in the designer (just moved class a little bit = change = auto-generated file will be re-generated after save) and saved. Now this particular DBML file is opened within a second. Try it.
Viewing the Toolbox and (optionally) resetting it (right click > Reset) seems to solve this. It seems the designer can't open when the toolbox is not initialised (or fails to initialise). It is often a while before I open the toolbox on a new install so I kept on encountering this problem.
I have a SSIS package with script task, and is created in VS 2015. I am able to edit script task and opens in VISTA (VstaProjects), set a break point and shows there. But when I close the VstaProjects solution, the breaskpoint disappears in Scripttask in dts package and if I run the task in debug never hits the break point. I am using,
SQL Server Data tool : 14.0.61712.050
SQL Server Integration servcie Designed 14.0.1000.169
Visual Studio Enterprise 2015 v 14.0.25431.01 Update 3
Specifically to the problem of breakpoints not saving in the project: ReSharper might be causing this issue if you have it installed.
For me, disabling "Debugger Integration" in ReSharper options fixed breakpoints not being saved when closing the VSTA project.
When you set the break-point, you must build the solution; save it; close VSTA; then click on OK. Failure to do any of these steps will wipe out the breakpoint.
See my answer here for more details. https://stackoverflow.com/a/49640300/4630376
I am running Visual Studio 2015 on a Windows 7 laptop, and every time I start up an application in the IDE's debugger I am presented with the following exception:
Unable to find an entry point named 'EventSetInformation' in DLL 'advapi32.dll'.
I have found reference to this in the coreclr repository on github indicating this is an API that was added in Windows 8. My case is similar to the github issue, and I can click 'Continue' to ignore the exception and my applications run just fine. However, this is really annoying because I can't just start debugging apps without waiting for this exception to get thrown so I can manually continue past it.
My question is whether anyone knows if I can prevent this exception from breaking in the IDE? This situation is just a nuisance at the moment, but one I'd love to get rid of.
For reference, in this case changing the Exception settings within Visual Studio doesn't seem to change the behavior. Here's screenshots for both enabling and disabling CLR exceptions, along with the exception:
CLR Exceptions disabled
CLR Exceptions enabled
Solution
This is caused by a general debugger option that seems to override any exception-specific setting. As indicated by #John in his answer below, there's a debugger option you disable to stop this behavior. When this option was checked I would get the break point described, but un-checking it stops that and provides what I was looking for:
By the looks of your screenshots, I would guess you have enabled the Debugger option "Break when exceptions cross AppDomains or managed/native boundaries". Go to Debugger->Options and uncheck that option (3rd from the top)
A co-worker just hit this issue and he had to check the 'Enable Just My Code' box found in Tools -> Options -> Debugging -> General along with clearing the check on 'Break when exceptions cross AppDomains or managed/native boundaries'.
See this screenshots, I have enabled the Debugger option "Break when s cross AppDomains or managed/native boundaries". Go to Debugger->Options and uncheck that option . Its work fine.enter image description here
Using keyhelp.ocx to display popup HtmlHelp in a modern Visual Studio C++ application fails.
I get a COM exception with no sensible error code. Looking at the debug output, there seems to be an Access Violation behind the scenes.
Your executable is build with Data Execution Prevention enabled, via /NXCOMPAT. That's the default in Visual Studio.
keyhelp.ocx is built using ATL7, which is incompatible with DEP - see http://support.microsoft.com/kb/948468
You need to disable DEP (/NXCOMPAT:NO) for your executable or find an alternative to keyhelp.ocx (I don't know of one).
(Note that's it's possible to enforce DEP system-wide - your code will still fail on such machines.)
I'm running visual studio express 2012 on Windows 7 through Bootcamp. I have a solution with several projects, and when I start debugging it runs the first project, but I can't start new instances of the others (when I right click and choose debug -> start new instance it is grayed out).
I tried creating a new solution with two blank projects and I have the same problem.
Any ideas?
Right click on Solution -> Common Properties -> Startup Project -> Multiple startup projects -> Choose "Start" actions in drop-down lists. Now start debugging as usual.
Right Click -> Debug -> Start New Instance is not available for all types of projects. Usually projects of the type class libraires have this option missing.
Thanks,
Karthik
Use the new instance of Visual studio in order to debug the other project.