visual-studio-debugging

XAML is not updating when debugging on a WP8 device

阅读更多关于 XAML is not updating when debugging on a WP8 device

I am experiencing a problem when deploying to a Windows Phone 8 device. It seems the XAML is not updating when I do a build and debug. The only way it seems to update is when I do a Rebuild > Debug or uninstall the app then debug. Here is a scenario: A page contains a button with a click event named "Button_Click". I debug and everything works. Stop debugging. Now change the event handler's name to NewButton_Click (yes, in both xaml and cs). Start debugging again, click the button and you get an exception because there is no event handler name "Button_Click" The XAML changes were not detected

Visual Studio 2015 Debugger Corruption - Is it a bug or just me?

阅读更多关于 Visual Studio 2015 Debugger Corruption - Is it a bug or just me?

Have I gone mad? I've always been able to trust the debugger right? Turns out that during a debugging session with VS2015, when I for example change the value of a variable in the Immediate Window, then that assignment results in a "garbage" value being assigned. It's the same garbage value every time, but completely wrong nonetheless. I've distilled this down to the simplest console application repro, and just in case you might think to concur with my self-assessment of madness, I've also made a screenshot video clip of it going awry. Are you guys getting this issue too or is this a local

Debugging not hit breakpoints in .NET CORE MVC 6 application

阅读更多关于 Debugging not hit breakpoints in .NET CORE MVC 6 application

I am working on .NET CORE 1.0 MVC 6 application and I stuck with the debugging point as it stopping hitting yesterday. with number of try I delete project and start again. First time it load symbols even due I have uncheck in Tool --> Debugging --> symbols, however it hit breakpoints. Now it only hitting C# class 'Startup.cs' if I choose 'Enable Just My Code' but in controller. I have Debug option from dropdown, not really sure why. Need help here. I change as Select Debug->Options->Debugging->General Tick Enable .NET Framework source stepping. but still no success Module Trying to Hit in

How to match a crash's “Fault offset” to the source code?

阅读更多关于 How to match a crash's “Fault offset” to the source code?

问题 An EXE I compiled keeps crashing. I have the following info in the Event Viewer when it crashes: Exception code: 0xc0000008 Fault offset: 0x00000000000cb8e8 How do I match the "Fault offset" with my C++ code? There is a .PDB file in the Release folder, just not sure what steps to figure this out. 回答1: You also need to know what module the offset belongs too, if you are getting 0xC0000008 ( STATUS_INVALID_HANDLE ), then the exception is likely thrown from ntdll.dll, which isn't going to help

Unknown identifier when using constants C#

阅读更多关于 Unknown identifier when using constants C#

问题 When im trying to use constants in this C# application. When i run through the debugger, the constants come up as an "unknown identifier" Heres the code public static class ConstsConfig { public static string BASE_URL_FORMAT = "%s://%s%s"; } public static class NetworkConfig { public static string PROTOCOL = "http"; public static string HOST = "www.example.com"; public static string BASE_URL = "/test"; } This is the line of code where its not evaluating it seems like Uri uri = new Uri(String

What is debugattach.aspx and why can't the server find it?

阅读更多关于 What is debugattach.aspx and why can't the server find it?

问题 I'm developing on an XP (SP3) machine with VS 2010 and IIS 5. I have two versions of the same site. We've released our first production version, so I forked the code into a new directory tree, and set up new virtual directories in IIS to point to the new trees. The projects are set up to run in the IIS rather than VS's server. The main site is an MVC 2 based project. My problem is that, when I hit F5 in Visual Studio 2010 to begin debugging the new version, I get a "Unable to start debugging

Visual Studio 2017 Debug Error: To prevent an unsafe abort when evaluating the function *.toString all threads where allowed to run

阅读更多关于 Visual Studio 2017 Debug Error: To prevent an unsafe abort when evaluating the function *.toString all threads where allowed to run

I updated Visual Studio 2017 to version 15.8.2. After this update, I started to encounter these errors while debugging: Here are the error messages: Visual Studio Debug Error: To prevent an unsafe abort when evaluating the function *.toString all threads where allowed to run. This may have changed the state of the process and any breakpoints encountered have been skipped. This error shows up quite often, and after a while Visual Studio crashes. I tried to uninstall and install Visual Studio again and reset preferences, but I had no luck. When I disable the option: "Enable property evaluation

Stack traces with async/await

阅读更多关于 Stack traces with async/await

问题 It's clear why stack traces are affected with Microsoft's new programming paradigm. We now have a semantic stack and a couple of physical ones (my choice of words). What I get to see is an exception's StackTrace property (and in the debugger) is the physical ones, concatenated: private async Task CheckFooAndBar() { var log = LogManager.GetLogger("Test"); log.Info("CheckFooAndBar"); try { await Foo(); } catch (Exception ex) { log.Info("StackTrace of last exception: " + ex.StackTrace); }

Why won't Visual Studio Debugger enumerate a BitArray and show me the results?

阅读更多关于 Why won't Visual Studio Debugger enumerate a BitArray and show me the results?

问题 For the following line of C# code: BitArray bitty = new BitArray(new[] {false, false, true, false}); If I evaluate "bitty" in the Watch window, I don't see the members of the collection. If I evaluate "bitty, results", which is supposed to enumerate the IEnumerable and show the results, I get the message "Only Enumerable types can have Results View", even though a BitArray IS an IEnumerable. Why does the debugger do this? CLARIFICAITON: I'm asking what is happening inside the VS Debugger

How can I avoid debugging into Boost source code in Visual Studio?

阅读更多关于 How can I avoid debugging into Boost source code in Visual Studio?

Is there a way to exclude boost source code (or any other) from debuging? I don't want to step into boost internal source code. for example: boost::shared_ptr<Xyz> xyz(new Xyz()); xyz->someMethod(); when I want to step into Xyz::someMethod() using F11 the debugger first steps into boost/shared_ptr.hpp before I get into Xyz::someMethod() Launch regedit and navigate to the following key: Under a 32bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0\NativeDE\StepOver Under a 64bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\NativeDE\StepOver Create a new