FastScriptReload
FastScriptReload copied to clipboard
Improved Debugger support - do not require to recreate breakpoints
Currently new file will be created for hot-reloaded code and breakpoints can be added there.
Alternatively in IDE wide function-breakpoint can be set referencing patched class name ChangedClass*_Patched*
This works but is rather bad user experience.
[ ] Investigate if existing Rider / VS integration packages can be patched by Harmony in a way that'd help improve workflow [ ] IDE plugin that allows to move existing breakpoints (big issue here is need to install additional IDE plugin) [ ] other approach? potentially if breakpoints can be read from Unity side maybe adding Debugger.Break in those lines would help?)
I wonder if it'd be possible to tamper with the pdb of the newly-compiled assembly to point to the original source file instead of the generated, compiled one...?
Not sure, would need to know a bit more how VS / Rider loads and work with PDBs under the hood