ExecutionTimer.cs not found when stepping into code

Question

I am writing some tests using XUnit framework and have to use some external code referenced through a dll.

When I try to step into the method call, helper.GetEntity(), I get the following window and the execution exits.

[Fact]
public void PassingTest()
{
    var datapointJson = File.ReadAllText(@"sample.json");
    dynamic datapointObject = JsonConvert.DeserializeObject(datapointJson);

    // This is referenced from a different project in the same solution.
    var helper = new Helper.Actions();
    var studentEntity = helper.GetEntity("tom");
}

Does anyone know why this is happening?

Can't you just click on *Continue*? That's not really an error, it's only a debugging message — Camilo Terevinto, Jan 05 '18 at 09:38
Well, that's the last line of the test, so it makes sense that it exits (there's nothing more to run) — Camilo Terevinto, Jan 05 '18 at 09:43
When I step into it, is debugger not supposed to go to the method definition? — Codehelp, Jan 05 '18 at 09:50
Do you have *Just my Code* enabled or disabled? Toggle that option, that should be the problem — Camilo Terevinto, Jan 05 '18 at 09:51
@Camilo That was it. Thanks and appreciate your time and help. — Codehelp, Jan 05 '18 at 10:08

score 28 · Answer 1 · answered Sep 18 '18 at 12:52

28

(posting @camilo-terevinto's comment as answer)

Turn on 'Enable Just My Code' in Visual Studio | Tools | Debugging | General.

answered Sep 18 '18 at 12:52

pauldendulk

1,378
12
23

1

But what is exactly happening? – Rich_Rich Nov 19 '18 at 13:48
4

I just got this with VS2017 and Resharper 2018.3.4. It didn't help to check "Enable Just My Code". It was enabled, I disabled it tried again and then re-enabled it and tried once more but it still stops. Has anyone else seen this recently? – Johan Bergens Mar 28 '19 at 15:25
@JohanBergens experiencing the same thing, and still haven't found a solution (2 days searching and counting..) :( – theCuriousOne Mar 29 '19 at 07:43
2

@JohanBergens actually I managed to fix it. See my answer below – theCuriousOne Mar 29 '19 at 10:00

theCuriousOne · Answer 2 · 2020-12-17T08:58:55.633

3

So I have been also struggling for 2 days with this one and nothing what I have found online helped me, but the answer of @pauldendulk guided me to the solution. Under Options -> Debbuging -> Just-in-Time I noticed that the "Managed" check box was unmarked and there was an warning label saying something like "multiple debuggers manes code ... please repair Visual Studio to restore ..." (sorry I didn't capture a screen shot and don't remember the right wording, but it was with that context).

After running repair of Visual Studio 2017 (Community Edition) via the "Visual Studio Installer" the test debugging worked like expected.

edited Dec 17 '20 at 08:58

answered Mar 29 '19 at 10:07

theCuriousOne

1,022
10
22

1

Had the same issue with debugging XUnit tests, didn't get the warnings you mention. Running repair of the Visual Studio helped, though. – voidengine May 23 '19 at 12:38

ExecutionTimer.cs not found when stepping into code

2 Answers2

Linked