Скачать или смотреть How to Get Your Blazor Wasm App Build Version at Runtime

Discover the best methods to retrieve your Blazor WebAssembly application's build version number at runtime, ensuring easy access to versioning information.
---
This video is based on the question https://stackoverflow.com/q/63999946/ asked by the user 'gp2gp2' ( https://stackoverflow.com/u/12625130/ ) and on the answer https://stackoverflow.com/a/64000293/ provided by the user 'Andy' ( https://stackoverflow.com/u/1204153/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Assembly build version at runtime in blazor wasm app

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Get Your Blazor Wasm App Build Version at Runtime

When developing a Blazor WebAssembly (Wasm) application, one common requirement is to track the application's build version. This is particularly useful for updates, debugging, and ensuring consistency across deployments. While in server-side Blazor you can easily access the assembly information using Assembly.GetEntryAssembly() method, the approach for client-side Blazor apps is slightly different.

The Challenge

In server-side Blazor, you might use a straightforward line of code like:

[[See Video to Reveal this Text or Code Snippet]]

This effectively retrieves the assembly version at runtime. However, in a Blazor WebAssembly context, the entry assembly may not represent the actual assembly that is running in the browser, leading to potential discrepancies.

The Solution

To correctly obtain the build version in a Blazor WebAssembly application, you should use the GetExecutingAssembly() method instead. This will ensure that you get the version information from the actual assembly that's executing.

Here’s How to Do It

You can retrieve the build version with the following code snippet:

[[See Video to Reveal this Text or Code Snippet]]

Why This Works

GetExecutingAssembly vs. GetEntryAssembly:

GetExecutingAssembly(): This method returns the assembly that contains the code that is currently executing. In the context of a Blazor WebAssembly app, this corresponds to your actual application assembly.

GetEntryAssembly(): In a client-side Blazor application, this does not yield the expected results since it refers to the assembly that started the application, which might not be the actual executable assembly you're interested in.

Use of AssemblyInformationalVersionAttribute:

The AssemblyInformationalVersionAttribute is used to store version information in a string format that can be easily accessed through code. This allows you to manage and display version information dynamically.

Automating Build Versions

If you are using a tool like the msbump package to automatically increment the version number with each build, you can ensure that the version retrieved using the above method will reflect the most up-to-date build version, maintaining version control with minimal effort on your part.

Conclusion

Accessing the build version of your Blazor WebAssembly application does require a different approach compared to server-side implementations. By using Assembly.GetExecutingAssembly() combined with AssemblyInformationalVersionAttribute, you can seamlessly retrieve accurate versioning information for your client-side applications. This practice not only aids in development but also enhances debugging and version tracking in production environments.

Whether you are maintaining an existing Blazor app or starting a new project, understanding how to effectively manage your build versions is a crucial skill that can streamline your development process.

For further inquiries or assistance, feel free to reach out or leave a comment below!