I've found that sometimes you need to manually delete the obj and bin folders and restart the ide to clear out errors sometimes. It's as if it gets stuck on a cache or something somewhere.
Yes, just doing a Clean is not enough.
I had to remove the Obj folder to get rid of signature errors.
It was with an older version though, maybe it is already improved.
Same here. I'm especially impressed with JetBrains' own implementation of Hot Reload.
I keep poking my head back into MSFT's Blazor tools (VS/VSC) every few updates and it feels like it just keeps getting worse and worse.
ok that worked for c# dev to goto the 1.x version but now i got razor errors
I thought blazor and vscode was mainstream enough where MS would want it to work right
There may be outdated references in one our your config files, I forget the specifics though. I've gone through this with Blazor/VS Code a few times, sometimes restarting the extension works, sometimes a clean build works, once I had to nuke and regenerate a bunch of config files
I've found that sometimes you need to manually delete the obj and bin folders and restart the ide to clear out errors sometimes. It's as if it gets stuck on a cache or something somewhere.
Same... but I'll try closing all my tabs, Clean/Rebuild, and reopening .razor file first, because sometimes that works.
Yes, just doing a Clean is not enough. I had to remove the Obj folder to get rid of signature errors. It was with an older version though, maybe it is already improved.
At my last job we had a powershell script for deleting those folders. We weren't even using Blazor at that point yet.
Get the same thing on full Visual Studio from time to time. The syntax parser is garbage for Blazor.
I ended up switching to Rider and it's way better.
Same here. I'm especially impressed with JetBrains' own implementation of Hot Reload. I keep poking my head back into MSFT's Blazor tools (VS/VSC) every few updates and it feels like it just keeps getting worse and worse.
Wish it was free
Try using Omnisharp with C# extension.. do not use C# Dev Kit
ok.. I thought that was the old version.. It turns out for Blazor you need to use that ?
ok that worked for c# dev to goto the 1.x version but now i got razor errors I thought blazor and vscode was mainstream enough where MS would want it to work right
Use the latest c# extension
I have the latest of everything.
You said version 1.x, that’s not the latest of the extension
i went back to v1 to see what happened. anyways i updated to latest.. same issue but it is livable
I've spent months troubleshooting this issue, even with the newly upgraded C# extension. Nothing works. Finally gave up and switched to Rider.
There may be outdated references in one our your config files, I forget the specifics though. I've gone through this with Blazor/VS Code a few times, sometimes restarting the extension works, sometimes a clean build works, once I had to nuke and regenerate a bunch of config files