Debugging in VS2017 - breakpoints not hit/cannot step into library project

Created at 31 Aug 2019, 15:18
Subscribe
How’s your experience with the cTrader Platform?
Your feedback is crucial to cTrader's development. Please take a few seconds to share your opinion and help us improve your trading experience. Thanks!
bishbashbosh's avatar

bishbashbosh

Follow

Joined 08.08.2018

Debugging in VS2017 - breakpoints not hit/cannot step into library project
31 Aug 2019, 15:18

I am debugging in VS2017 and have a vanilla C# class library project included in the solution.

I can set breakpoints and step into the code in all other projects apart from this one (it's the only one that wasn't created by cTrader itself). When I look at the stack trace it says "External Code".

To confirm, all the build configs are set to Debug across the board.

Any suggestions?

@bishbashbosh
Replies

srubtsov
31 Aug 2019, 15:45

Adding that code to the end of AssemblyInfo.cs of a class library project should help you

#if DEBUG
[assembly: Debuggable(DebuggableAttribute.DebuggingModes.Default | DebuggableAttribute.DebuggingModes.DisableOptimizations)]
#endif
@srubtsov

bishbashbosh
06 Sep 2019, 17:32

Excellent. Thank you very much.

@bishbashbosh
Copyright © 2024 Spotware Systems Ltd. All rights reserved.
cTrader Ltd offers through its group of companies the cTrader platform. The information on this website is for general informational purposes only and does not constitute financial or investment advice. cTrader does not solicit retail investors. Reliance on this information is at your own risk.