Aspnetcore: [Server-side] Adding 'namespace' will prevent the debug session from continuing.

[vertonghenb]

When debugging from time-to-time (especially when debugging components)
The following error pops-up:

Adding 'namespace' will prevent the debug session from continuing.

Although I haven't changed anything to the codebase, only stepping into and over functions.

The component itself is a GenericComponent introduced in Blazor 0.6.0.
Restarting Visual Studio, seems to solve the problem but from time-to-time the issue rises again.

Edit:
Removed component code, doesn't help at all.

[danroth27]

@vertonghenb What version of VS are you using? Also, does this happen when running client-side or server-side? Also, where do you see this error pop up? Does this show up in a VS dialog or somewhere else?

[vertonghenb]

VS Enterprise 2017
Version 15.8.8

The error arises while using the Server Side Model.
The error is shown in the Error List Window, and shows a pop-up to edit the code or stop debugging.
If the error happens again, i"ll send a screenshot.

[danroth27]

Repro steps:

• Create a default Blazor server-side app
• Set break points in the IncrementCount method, in OnInitAsync and in the foreach loop in the FetchData component
• Debug and step through the code

Actual result:

[danroth27]

Also repros with 15.9 Preview 4.

[vertonghenb]

@danroth27, exactly! Doesn't happen all the time though.

[grantnilsson]

I am still seeing this with 2017 v15.9.3. It happens mainly in cshtml code for me when an exception is generated in the code. You can not go anywhere as it thinks the nsamespace has changed - so options at this point are Edit code, or Stop debugging... Very annoying
Maybe the namespace of the eception handling is causing the issue

[vertonghenb]

Seems to be a tooling issue, maybe close this one in favor of this: https://github.com/aspnet/AspNetCore/issues/5017

[baartho]

This issue is still happening in preview 8. It is a huge productivity breaker. It would be greatly appreciated if this was fixed.

[loganmarshall1]

Still not fixed in 16.3.0

[alexveya]

Very annoying error. Need to stop debug every time you open a new file during debuging.

Would you ever fix it?

[loganmarshall1]

Agreed! Super Annoying! If Microsoft cares about global developer productivity with core/mvc it would be important to them to fix. So I know a fix is coming. :)

As a temporary poor work around we run without debugging so we can edit razor files without this error.

We also debug run the project in VS Code and edit the razor files in VS 2019.

Hope these 2 poor work around are helpful to people that are tired of this error not being a priority to be fixed.

Thanks!

Logan

On Oct 2, 2019, at 5:02 AM, alexveya [e-mail] wrote:



Very annoying error. Need to stop debug every time you open a new file during debuging.

Would you ever fix it?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/aspnet/AspNetCore/issues/5621?email_source=notifications&email_token=AEYSEOCLOZFW3E6V7YRGS7DQMRPQTA5CNFSM4GK46TJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAECAYQ#issuecomment-537403490, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEYSEOFXSXRWWMAOB2BACPTQMRPQTANCNFSM4GK46TJA.

[shapeh]

Getting the same in VS 2019 Community - v. 16.3.3. Windows 10 Professional.
It happens in .cshtml files and standard .cs classes.

[loganmarshall1]

Still not fixed 16.4 Preview 2.

Millions of global dotnet core/mvc/c#/razor developers effected.

Billions of hours lost to having to restart build because of breakpoints.

[JasSra]

Can we have a fix please, loosing too much of time in tooling rather than focusing on development

[TPucke]

+1 for priority here
16.3.5

[satyambhatt]

Same Problem I found my VS2019

[MiheevN]

16.3.6... Why...😣😥😥😥😭

[wangpengzong]

have the same problem here, I can see the error message only when debugging.

My friend told me that there may be the following reasons:

1. Changed the code inside the delegate;
2. Introduced a new namespace;

But these two actions in the project can not be avoided, how to solve?

[staa99]

It's still here in 16.3.1
Why isn't it fixed yet? this issue has been around for over a year.

[Seabizkit]

is this still a thing? 16.3.8

[loganmarshall1]

Still not fixed in 16.3.9.

Apparently the fix is in 16.4 previews right now, but when we tested those previews this bug was still happening.

Let's pray it gets fixed in 16.4 GA. :)

Logan

On Nov 13, 2019, at 9:16 AM, Seabizkit [e-mail] wrote:



is this still a thing?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/aspnet/AspNetCore/issues/5621?email_source=notifications&email_token=AEYSEOHHZGP53CM5TJDCPO3QTQD3NA5CNFSM4GK46TJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED6I2MA#issuecomment-553422128, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEYSEOG63KW3Z2A53TGM7QLQTQD3NANCNFSM4GK46TJA.

[FTalour]

Temporary fix :

To continue your debug session click on the error and then delete the generated code.

Hope it helps you.

[Enriquecerviro]

Is this still alive? not the thread, the feature I mean

[Seabizkit]

Is this still alive? not the thread, the feature I mean

bug you mean, and I'm pretty sure that the

Temporary fix :

To continue your debug session click on the error and then delete the generated code.

Hope it helps you.
...

does not work, as the issue is it randomly detects changes in JS, files or what ever file, aka there is no change, there is nothing to undo. I think you maybe experiencing something else.

now i come into this issue when i started working on another teams code, which was all over the place.... in terms of having what i consider weird ways of working, anyway i have not been active in the code base, so cant say whether or not it has been dealt with.

[Speedocs]

This bug is still there in VS Enterprise 2019 16.3.10.

For me it only happens if I break inside a cshtml file, and if I remove the breakpoint I can continue normally.

This is a terrible productivity killer and it is unfortunate that this bug has not been resolved in over a year.

[loganmarshall1]

It's fixed in 16.4 please update. We've been setting break points in razor and it works great! :)

Logan

On Dec 31, 2019, at 4:31 AM, Ido Kalir [e-mail] wrote:



This bug is still there in VS Enterprise 2019 16.3.10.

For me it only happens if I break inside a cshtml file, and if I remove the breakpoint I can continue normally.

This is a terrible productivity killer and it is unfortunate that this bug has not been resolved in over a year.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/aspnet/AspNetCore/issues/5621?email_source=notifications&email_token=AEYSEOH2TT3IP4AIISHOTDLQ3MGPFA5CNFSM4GK46TJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH366JA#issuecomment-569896740, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEYSEOEPX7YFGLFIKN6SHELQ3MGPFANCNFSM4GK46TJA.

[SteveSandersonMS]

I believe this was fixed a while ago, and VS WebAssembly debugging has moved on a long way since then. Closing.