Debugging Blazor Applications



We will be discussing how to debug both a server side Blazor application as well as a Client-side Web Assembly application.

Client-Side Web Assembly


To debug this type of application we will be using the browser tools to access the C# code.  As of this post, only Chrome supports debugging the web assembly client application.  Microsoft Edge can be used, but it just fires up a chrome instance to debug with.

Steps to debug:

      1.  Create a client-side web assembly application from the standard Blazor templates that are provide with Visual Studio or Visual Code
      2. Run application in Chrome
      3. Press F12
      4. You will see a comment to press Shift – Alt – D to debug
      5. Make sure you click on the actual Blazor application
      6. Press Shift-Alt-D
       7. A new browser tab will be displayed.
a.       If you do not see any errors, congratulation you are good to go.  Jump to step 8.
b.       If you see this error, Follow the steps below


c.       You need to copy the URL highlighted.  Please note that your URL will be different, and you need the listed for your projects.
d.       Close ALL the Chrome browsers you have open
e.       Go to the task manager and look for any Chrome related process running and kill those
                                                               i.      All chrome processes must be stopped to get this to work
f.        Press Win+R
g.       Paste in the URL and press enter
h.       Press Shift-Alt-D
      8. A new developer tab will be displayed
      9. Go to source
a.       Select the file:// node and expand
b.       Expand the “Pages” node
c.       Click on Counter.razor
d.       You should be able to see your C# code.


      10.   Set a break point on currentCount++
      11.   Go to the Counter page in the application
      12.   Click the “Click me” button and see the browser hit the break point
      13.   You can now step through the code like any other client-side debugging session.

 Server-side Application

The server side is much easier to debug.  You debug it like a normal server-side application.

Steps to Debug

       1.       Create a client-side web assembly application from the standard Blazor templates that are provide with Visual Studio or Visual Code
       2.       Run application in Chrome
       3.       In Visual Studio
a.       Set a break point on the currentCount++ line.
       4.       Go to the Counter page in the application
       5.       Click the “Click me” button and see the browser hit the break point

       6.       You can now step through the code like any other Visual Studio debug session.

Following this steps you should be able to debug either type of Blazor application.  I have found if I can walk the code it make things so much easier to understand.


Comments

Post a Comment

Popular posts from this blog

Yes, Blazor Server can scale!

Image
From the very beginning of the release of Blazor Server naysayers have incorrectly stated that Blazor Server can not scale.  They usually state that the limit is 5,000 concurrent users. There are several misconceptions and wrong assumptions about their statement.  Let's break it down and get a better understanding of Blazor server-side scaling. What is the "limit" for users When Microsoft talks about the need to scale an application, what they are saying is that when a normal response for any concurrent user is taking longer than 200 ms, the system is not performant and needs to scale. We will accept that definition: If any normal user response is taking longer than 200 ms, the system needs to scale for concurrent users. By a normal response, we are referring to a page get, a post, etc.  Large database access requests would not be included in this measurement. What is scaling There are 2 common ways to scale, scale, out horizontally, and scale-up, up vertically. In our di
Read more

Blazor new and improved Search Box

 Back in March, I posted a new Blazor data grid with a search box ( see post ).  Since then I have found a new and improved search box that I wanted to implement.  The search part is implemented the same.  What I added was the ability for the user to narrow down the search by selecting which field they wanted to search on.  This will help the user find what they are looking for and in a large collection, the search will end up being faster. The goal of making the change was to make the search box a new component and have it handle the UI functionality part. Prep Work Here is the prep work I did before adding the search box: Started with the source code from the post listed above. Upgraded the project to .Net 5 Upgraded the Nuget packages that were out of date. Ensured every build and run. Change to a Component I wanted to create a component for the search box so I could use it in other applications.   1. Create a Folder under UIControls called "SearchBox" 2. Created a new raz
Read more

Blazor - Cool Blur Loading Page

Image
  I was working on a project and wanted an original way of showing the user the application was loading besides using the normal "Loading...." text.  I came across a website page and thought I could refactor that into what I was looking for. When my application starts, it displays a full-screen image with a count down while the page loads.  As a special effect, I want to unblur the image the closer it gets to the applicaiton finishing loading.  Once the teh count down is done, we pause for 1 sec, for effect, then proceed to the application.  I think it turned out pretty cool.  See the demo here . I used the server side Blazor project template in my example, but the code should work on any Blazor template. Template changes 1. Rename the original Index.razor page to "home".  Besure to change the routing at the top of the page as well.      @page "/home" 2. Create a new Index.razor page     a. Add routing           @page "/"           @page "/i
Read more