I am debugging a service, so I use a Debug.Launch() call to attach the debugger. I change a dependent dll.
Visual Studio behavior after each change in the source code is either:
- it does not pick up the recent change during each first run and disables breakpoints with message 'The source code is different from the original version'. When I restart the service the breakpoints are enabled, or -
- dropping and recreating the breakpoint enables it.
- this repeats after each change in the source code.
I verified that the right pdb is loaded to the debugger on each run; date and time of the pdb file matches the exe.
Debug output log also shows the symbols are loaded; Debug / Modules shows the right location of dll and pdb. I think I made XDesProc.exe not starting by default by setting the "Always open documents in full XAML view", just to exclude it from the
process.
Please help, this issue kills my performance. Cleaning up and rebuilding the solution does not resolve the problem. Restarting VisualStudio resolves the problem but I am seeking a practical solution.
Also to note, I manually build the dll in question, so the 'buld' option is turned off at the solution properties. I do not see a reason to turn it on, unless Debugger checks that option out for some awkward reason. Test changes I do involve that one dll only, no any dependencies are changed.
Please advise.
Alex
Regards
UPDATE: I actually have the build option turned on for this dll at solution properties, although I build it manually after each change.