Каковы недостатки поддержания работы приложения во время длительного процесса отладки? [закрыто] ⇐ C#

[Anonymous]

As you all probably know, our step-by-step Debugging efforts can take a sizeable amount of time. It often serves us to take that time while our App is running and 'waiting' for us to eventually hit the 'Continue' button.

Question: Are there 'costs' (for example in terms of resources, memory, etc...) to keeping an App 'waiting' for what may turn out to be a very long stretch while one continues to step through many lines of code; perhaps even re-writing code while one is doing the 'stepping'?

Please note, I've been encouraged by a StackOverflow moderator to be mindful of framing this question in a way that makes it clear I'm not asking for 'opinions'. So, if this helps, please know I'm not asking for your general 'feelings' about what methodology happens to work better for you personally. I'm actually asking a 'technical' question. Are there 'technical' reasons for not keeping an App 'waiting' for long stretches while you slowly move through intricate Debugging?


Источник: https://stackoverflow.com/questions/780 ... ng-process