WebVella.BlazorTrace 1.1.0

What is BlazorTrace?

An easy to add library that will enable you to get detailed information about your Blazor components rerenders and memory, as well as compare it with different snapshots that you created. It is targeting Blazor UI developers and presents the information in a simple and focused way. BlazorTrace will help you develop better, faster and more consistent user experience with your Blazor applications.

About Us

We are a small team of early Blazor adopters that created several complex Blazor applications that work in production. We prefer working with WebAssembly deployments but SSR is getting a favorite fast. We have 15+ experience in creating .net projects. Here is some examples of our work

WebVella ERP
Document Templates Library
Tefter
Npgsql.Extensions

How to get it

You can either clone this repository or get the Nuget package

Please help by giving a star

GitHub stars guide developers toward great tools. If you find this project valuable, please give it a star – it helps the community and takes just a second!⭐

Documentation

You can find our documentation in the Wiki section of this repository

Get Started

To start using BlazorTrace you need to do the following simple steps:

1. Add the latest version of the WebVella.BlazorTrace Nuget package to your component holding projects directly. It is important to be directly referenced, so the FodyWeavers.xml and WvBlazorTraceModule.cs can be generated in the projects root!
2. Add the following lines in your Program.cs file. You can get more info about options to fine tune or extending SignalR hub size for larger snapshot in the wiki.

builder.Services.AddBlazorTrace();

3. In your _Imports.razor file add the following lines so all supported components can start being monitored

@using WebVella.BlazorTrace;
@attribute [WvBlazorTrace]

4. Add the BlazorTrace component at the end of your App.razor or Routes.razor component (depending on your project type)

<Router AppAssembly="@typeof(App).Assembly">
...
</Router>
<WvBlazorTrace/> @* <-- INSERT HERE *@

5. Rebuild the solution
6. Thats it. You can start reviewing the data. PRO TIP: Use the F1 (show) and Esc (hide) to save time.

Method OnEnter/OnExit call information

Log signals information

Trace calls detail information

Memory detail information

Limit hits

Snapshots

Muted traces

License

BlazorTrace is distributed under the MIT license.

Acknowledgments

BlazorTrace wouldn't be possible without the incredible encouragement and support of amazing people and communities. Thanks to all of you!

jhsheets

For being our fist contributor and thus boosting our motivation to make BlazorTrace better.

LlamaNL

He saved time to all of us, by finding a way how to create faster tracer intergation with an Attribute and FODY

Tension-Maleficent

For helping with the FODY implementation

/r/dotnet, /r/Blazor, /r/csharp

These Reddit communities are home to incredibly welcoming and knowledgeable people, always ready to offer help with questions, problems, or advice.