Hi @Deepak_Jamwal ,
AFAIK, that's not possible by native NAV debugger. If you know the dll file which one you use to catch this variable, you can easily decompile it by free decompiler to see source code (but not to debug it), e.g. https://www.jetbrains.com/decompiler/
If you don't know the dll file - go to google, find where your variable is located, and again use decompiler.
Using Visual Studio open the solution. Then under Debug > Attach to process > NAV Client/Server. Then when your component gets called you can use breakpoints to step thru the process.
Using DotPeek you could also reverse engineer a dll. However doing this could mean you are breaking some rules/agreements about the usage of software/licenses.
Answers
AFAIK, that's not possible by native NAV debugger. If you know the dll file which one you use to catch this variable, you can easily decompile it by free decompiler to see source code (but not to debug it), e.g. https://www.jetbrains.com/decompiler/
If you don't know the dll file - go to google, find where your variable is located, and again use decompiler.
can you please elaborate it.
Hm. What do you want me to elaborate?
Using DotPeek you could also reverse engineer a dll. However doing this could mean you are breaking some rules/agreements about the usage of software/licenses.
Doesn't your method work only if we have dll source (solution)?