Visual Studio Community 2019 Debugger Not Preempting Chrome Debugger with Blazor Wasm App - google-chrome

I am playing with a Blazor Wasm app on VS Community 2019 v16.6.2 using AspNetCore v3.2.0 and Chrome v83.0.4103. When I set a break point in some native javascript in VS, Chrome breaks on that statement instead of VS as shown in the screenshot below (look for the small light yellow "Paused in debugger" popup). This has happened before, but then I discovered I had '"nativeDebugging": true,' in the IIS Express profile in launchSettings.json. I got rid of it, and the problem went away. Now it is back, without nativeDebugging set. This is a giant pain. Any idea what I am missing this time?
Thanks. Steve

I'm not sure this is a real answer. As I said above, the problem went away when I merely opened the .map file for the TypeScript file. I assume that triggered some rebuild-like process, but that's purely conjecture.

Related

Visual Studio 2022 hangs when open Razor file

Created a stock Blazor project (Client or Server side, both do it).
When I open the _Imports.razor, not a problem.
Open NavMenu.razor, a problem.
The IDE opens the file, displays formatted Razor and after a couple of seconds just hangs, CPU usage for devenv.exe goes 50% and stays there until End Task.
Any idea how to fix this? The IDE should not hang when I try and work with a Razor file.
Thanks to the effort by these guys, changing the IDE font from 'Cascadia Mono' to Consolas sorted the problem:
https://youtrack.jetbrains.com/issue/RSRP-487353/Visual-Studio-2022-stops-responding-when-used-with-Resharper
(Note: Not using Resharper, stock VS2022 install)

Opened VS 2013 Solution in VS 2017. Now Razor intellisense doesn't work

So, I have an MVC 3 web project/solution for VS 2013. I decided to open it in VS 2017, get all modern. Visual Studio did it's thing. Note I did NOT upgrade the MVC versions, I was content to stay at 3 and Razor at version 1.0.
Now, when I open up my cshtml pages, all the Razor syntax has squiggly red lines. If I F12 on the #Html in my cshtml page, it takes me to System.Web.WebPages.WebPage instead of System.Web.Mvc.WebViewPage as it is supposed to.
I've researched this a lot. And I've tried pretty well everything out there. I've deleted the obj and bin folder contents, wiped out the ComponentModelCache, and the .vs folder, and the .suo file. I don't have Resharper on 2017. I've checked the .config files, and all seems in order; all appear to have the correct references.
I'm really at my wits end here. This is incredibly annoying. I'm hoping someone out there has a better answer than what I've found to date.
Any help appreciated. I really don't want to have to roll it back to VS 2013, but I might just have to.
Regards,
You need to upgrade the Razor / MVC versions to versions that VS2017 supports.

Changes not visible when running debugger, web development VS 2013

I'm having periodic issues with changes I make to a website I'm building with VS not showing up when I run the VS debugger. For example, sometimes if I delete a section of code it still appears when I run the code using the VS debugger. This issue doesn't happen that often, and seems to appear and disappear randomly. If I go into the project's folder and manually open (double-click) the .html page I'm working on I can see my changes, so I know it's an issue with VS.
Is there something obvious I'm missing? I've just started using VS for web development, and as far as I know I'm using all the default settings.
Thanks!
Clean and built your project and try again dude.

Resharper 8 slows down the vs 2013 razor editor

I having problems with resharper in visual studio 2013 razor editor. Trying to move to another line of code with mouse gets about 1 sec to complete. Moving with arrows is a bit faster. Intelisense and code completion is very slow also.
I'm using an Core i7, 12GB DDR3, RAID0 SSDs PC.
Any help would be appreciated.
Thank you.
I had the same problem. I manage to solve this by following the steps in this blog.
I didn't have to do all of the steps. The step that "saved" me was
Disable "Rich client visual experience" in the "Options -
Environment". Here's how that settings page should look:screenshot
I hope this will solve your problem.
The solution (Disable "Rich client visual experience" ) does not work for me.
I noticed that the problem only occurs when a document is reopened. If the document is already open when you open the Solution not the problem occurs.
Devexpress published an update to their vs menu integration (i think) which solves the problem.
https://www.devexpress.com/Support/Center/Question/Details/Q561434
Thank you all.

VWD 2010 express in Windows 7 design mode problems

So far I was using VWD 2010 express quite smoothly on Windows XP. Now I have got a new laptop - with Windows 7 64 bit. Yesterday I installed VWD 2010 express. I transfered all my data to the new laptop. When I open an existing project, it opened well and even runs very well. But when I am design mode I have lots of problems like
Cursor is not seen in the .aspx page and scrolling does not work. Cant edit anything. However .aspx.cs works normally
when I press Ctrl + F, Find window opens up but when I give find next, the instance is not seen and the page does not navigate to the instance
When I double click on a file in the solution explorer, i dont see it open. But when I minimise the entire VWD and maximise it, I see that the clicked page is open.
sometimes (mostly just after the project is loaded) part of the screen is black and when i minimise VWD and maximise, the page is properly shown.
I tried Repair and also uninstalled and reinstalled the entire VWD 2010 express - the problem still exists. I dont know what problem it could be. I did not encounter any problem while installing VWD. Could this be a VWD problem or memory problem (8GB RAM) or graphic card(dedicated) problem? Any help is highly appreciated.
I solved the issue yesterday, I logged in to the forum today to post my solution so that it helps someone later. Here is what I did:
I opened the "Compatibility Troubleshooter" in the control panel and identitified that there is a compatibility issue. So I made changes to open VWDexpress in the compatible mode (In my case it was Windows XP service pack2) and saved the settings. Now it works very well.