Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
VS Code debugger in wrong place on standard code - BC v23
garmoo
Member Posts: 21
When debugging, I go through several functions of bespoke code and everything works fine. Stepping into, over and out all fine, but when I get to here
and step into the standard Sales Header table code, it brings me here
I believe it is debugging the correct lines in the background, it's just not taking the Namespace ___ using ____ lines into account in what lines its showing. Anybody any idea how to resolve this? It's particularly annoying as the code it's actually stepping through is so far down that I have to scroll down every time I change line if I want to read it.
and step into the standard Sales Header table code, it brings me here
I believe it is debugging the correct lines in the background, it's just not taking the Namespace ___ using ____ lines into account in what lines its showing. Anybody any idea how to resolve this? It's particularly annoying as the code it's actually stepping through is so far down that I have to scroll down every time I change line if I want to read it.
0
Answers
RIS Plus, LLC
You need to update your BC to a version higher than 23.1
Yes, it is, It's a BC bug