The “Where-Used” in Visual Studio Code is nice, but not always productive. Today I wanted to see where a field was used and came up with an alternative I wanted to share.
ObsoleteState
If you mark a field ObsoleteState::Pending the compile will throw warnings everywhere the field is used. This allows you to quickly use the error window to jump through the code and check whatever you want…
Continue Reading Mark Brummel’s Article on their blog
Tip #62 | “Where-Used” in Visual Studio Code
The “Where-Used” in Visual Studio Code is nice, but not always productive. Today I wanted to see where a field was used and came up with an alternative I wanted to share. ObsoleteState If you mark a field ObsoleteState::Pending the compile will throw warnings everywhere the field is used.
Blog Syndicated with Mark Brummel’s Permission
More About This Author
Array
- Business Central3 December 2021Best Practices for (Per Tenant) Extensions | Protect Yourself
- Business Central2 December 2021Oh, TempBlob! What did you do?
- Business Central1 December 2021“GENERIC METHOD” | Brilliant or Anti Pattern?
- Business Central28 November 2021Using Azure Log Analytics on older Dynamics NAV versions