1

Topic: VS2017 - A problem at debugging

At pushing Step, permanently springs from one flow on another. At me any local problems, or a functional simply broke it?... <<RSDN@Home 1.0.0 alpha 5 rev. 0>>

2

Re: VS2017 - A problem at debugging

Hello, CoderMonkey, you wrote: CM> At pushing Step, permanently springs from one flow on another. At me any local problems, or a functional simply broke it? If the heap of flows fulfills the same code, this normal behavior.

3

Re: VS2017 - A problem at debugging

Hello, CoderMonkey, you wrote: CM> At pushing Step, permanently springs from one flow on another. At me any local problems, or a functional simply broke it? It so always also worked. If it is necessary, open debug-> windows-> threads and deliver on a pause all flows which hinder you.

4

Re: VS2017 - A problem at debugging

Hello, Sharowarsheg, you wrote: S> It so always also worked. Here  write that so should not be. Though, maybe, simply tell lies. https://visualstudio.uservoice.com/foru … hread-inst Additionally, I wanted to clarify that the debugger will only ever complete a step on the thread from which the step was originated. So if you hit a breakpoint, disable it, and then begin stepping you should not stop on a different thread.... <<RSDN@Home 1.0.0 alpha 5 rev. 0>>

5

Re: VS2017 - A problem at debugging

Hello, CoderMonkey, you wrote: S>> It so always also worked. CM> here  write that so should not be. Though, maybe, simply tell lies. CM> https://visualstudio.uservoice.com/foru … hread-inst CM> CM> Additionally, I wanted to clarify that the debugger will only ever complete a step on the thread from which the step was originated. So if you hit a breakpoint, disable it, and then begin stepping you should not stop on a different thread. Strange. All versions of studio at me springed on step over between flows. I do not know, who such Kaycee Anderson, but my experience says that it is not right.

6

Re: VS2017 - A problem at debugging

Hello, Sharowarsheg, you wrote: S> I do not know, who such Kaycee Anderson, but my experience says that it is not right. Well like as the official representative of Visual Studio Team... <<RSDN@Home 1.0.0 alpha 5 rev. 0>>

7

Re: VS2017 - A problem at debugging

Hello, CoderMonkey, you wrote: S>> I do not know, who such Kaycee Anderson, but my experience says that it is not right. CM> well like as the official representative of Visual Studio Team CM> Additionally, I wanted to clarify that the debugger will only ever complete a step on the thread from which the step was originated. So if you hit a breakpoint, disable it, and then begin stepping you should not stop on a different thread. The Keyword is selected Actually AFAIK  it is necessary all break points, but there probably meant that it of all one

8

Re: VS2017 - A problem at debugging

Hello, bnk, you wrote: bnk> the Keyword is selected bnk> Actually AFAIK  it is necessary all break points, but there probably meant that it only one Even if all of them generally to delete, all the same springs between flows.... <<RSDN@Home 1.0.0 alpha 5 rev. 0>>

9

Re: VS2017 - A problem at debugging

Hello, CoderMonkey, you wrote: CM> Hello, bnk, you wrote: bnk>> the Keyword is selected bnk>> Actually AFAIK  it is necessary all break points, but there probably meant that it only one CM> Even if all of them generally to delete, all the same springs between flows. . At me simply remaining flows scrolls, but does not spring. Or? http://files.rsdn.org/11344/step.gif

10

Re: VS2017 - A problem at debugging

Hello, bnk, you wrote: bnk> http://files.rsdn.org/11344/step.gif the Test too small.... <<RSDN@Home 1.0.0 alpha 5 rev. 0>>

11

Re: VS2017 - A problem at debugging

Hello, CoderMonkey, you wrote: CM> Hello, bnk, you wrote: bnk>> http://files.rsdn.org/11344/step.gif CM> the Test too small. . Like if it springed, it like would spring on the first step where "2". Or you mean that it casually happens?

12

Re: VS2017 - A problem at debugging

Hello, bnk, you wrote: CM>> the Test too small. bnk> Hm. Like if it springed, it like would spring on the first step where "2". bnk> Or you mean that it casually happens? Yes. At first, not always; secondly, apparently, springs when more GC more.

13

Re: VS2017 - A problem at debugging

Hello, CoderMonkey, you wrote: CM> At pushing Step, permanently springs from one flow on another. At me any local problems, or a functional simply broke it? So is  to studio which helps to debug one flow without springing, and so it  behavior of studio

14

Re: VS2017 - A problem at debugging

Hello, codenet, you wrote: the C> so is  to studio which helps to debug one flow without springing, and so it  behavior of studio DebugSingleThread

15

Re: VS2017 - A problem at debugging

Hello, Sharowarsheg, you wrote: CM>> Here  write that so should not be. Though, maybe, simply tell lies. CM>> https://visualstudio.uservoice.com/foru … hread-inst CM>> CM>> Additionally, I wanted to clarify that the debugger will only ever complete a step on the thread from which the step was originated. So if you hit a breakpoint, disable it, and then begin stepping you should not stop on a different thread. S> it is strange. All versions of studio at me springed on step over between flows. I do not know, who such Kaycee Anderson, but my experience says that it is not right. To my astonishment, at least in 13th studio it is right. If the flow got on bp after to remove (or disable?) bp, further it is possible to walk easy this flow. Live and learn. I all life  flows, marked  etc. the Pancake.

16

Re: VS2017 - A problem at debugging

Hello, Sharov, you wrote: S>> it is strange. All versions of studio at me springed on step over between flows. I do not know, who such Kaycee Anderson, but my experience says that it is not right. S> to my astonishment, at least in 13th studio it is right. If the flow got on bp after to remove (or disable?) bp, further it is possible to walk easy this flow. Live and learn. S> I all life  flows, marked  etc. the Pancake. And what target framework? Because I spring all the same - as soon as GC begins, and starts to spring.

17

Re: VS2017 - A problem at debugging

Hello, Sharowarsheg, you wrote: S> And what target framework? Because I spring all the same - as soon as GC begins, and starts to spring. 4.5.2