Changing the Platform Target to x86 works for me, It came to a point that stepping through the code was impossible without the forementioned Exception. I run Win 8.1 64-bit and Visual Studio 2013.
More Related Contents:
- Easier way to debug a Windows service
- Why does .NET add an additional slash to the already existent slashes in a path?
- #if DEBUG vs. Conditional(“DEBUG”)
- How can I make something that catches all ‘unhandled’ exceptions in a WinForms application?
- Performance differences between debug and release builds
- Capturing console output from a .NET application (C#)
- Cannot step into .NET framework source code
- The breakpoint will not currently be hit. No symbols have been loaded for this document in a Silverlight application
- Visual Studio debugging “quick watch” tool and lambda expressions
- Don’t stop debugger at THAT exception when it’s thrown and caught
- What is a thread exit code?
- Unable to connect to ASP.Net Development Server issue
- How can I see what my reactive extensions query is doing?
- Is there a way to detect if a debugger is attached to another process from C#?
- User Activity Logging, Telemetry (and Variables in Global Exception Handlers)
- Trying to debug Windows Store App from dump files
- Cannot find .cs files for debugging .NET source code
- How do I see the raw HTTP request that the HttpWebRequest class sends?
- Blue screen when using Ping
- Why can I not edit a method that contains an anonymous method in the debugger?
- Debug Windows Service
- Attach Debugger to IIS instance
- What is an “Async Pinned Handle”?
- LOH fragmentation – 2015 update
- How can I include line numbers in a stack trace without a pdb?
- Visual Studio 2015 RTM – Debugging not working
- Will #if RELEASE work like #if DEBUG does in C#?
- Trace vs Debug in .NET BCL
- Visual Studio 2015 diagnostics tool does not support current debugging configuration
- Should I compile release builds with debug info as “full” or “pdb-only”?