Blazor Server Side vs Client Side Debugging

Server Side Debugging Breakpoints can be reached from within Visual Studio. Client Side Debugging Breakpoints can not be reached within Visual Studio. Need to setup Breakpoints from within browser debugger. (Shift + Alt + D) Note: For Client Side Debugging, you may need to run browser in debugger mode using command line. You will see... » read more

Debugging Blazor WebAssembly App from within Browser

Client Side Debugging Make sure the Startup Project is set to MyApp01.Client project. Not the server project. Run debugger and press Shift + Alt + D Error message will pop up saying unable to find debuggable browser tab. Copy the command line code and run in command console. A new browser will be launched in... » read more

Debug Azure Web App using Kudu

Using Kudu First, let’s launch Kudu. You can do this in a variety of ways. Here are a few: Launch Kudu manually from the address bar If your website is https://magicalunicorns.azurewebsites.net, the Kudu URL is https://magicalunicorns.scm.azurewebsites.net. Notice the appended “scm.” here. You’ll need to be signed in with an account with access to the App Service resource... » read more

Error: You are debugging a release build

Error: For some reason, when I launch this application in the debugger using the normal Start Debugging command in Visual Studio, it launches, but it also produces the following warning: Resolution: Disable this option under Debug->Options->Suppress JIT optimization on module load (Managed only). Sources: https://stackoverflow.com/questions/38601643/error-you-are-debugging-a-release-build-of-x-dll