3 ms·
IME it can be unreliable and just doesn't end up being all that useful. C# compile times being what they are, it's not such a burden to stop and rerun for minor
by mystified5016 2y ago
IME it can be unreliable and just doesn't end up being all that useful. C# compile times being what they are, it's not such a burden to stop and rerun for minor changes.
Not like my C++ projects which take several minutes to build because Windows Defender wants to use 50-80% of my CPU to monitor the compiler for malware. Wish I could hot reload one TU or something.
- NikkiA 2y agoI have used it a few times for debugging, as long as you are aware that it's not a guarantee that your changed code works perfectly when run from scratch, it can be useful to iterate changes to a single function without a whole compile>build>debug cycle, just edit the code and see if it changed the behaviour in the debugger.