repository·master·Indexed 27 days ago
https://github.com/dotnet/blazorDocumentation for the Blazor web framework repository, focusing on build tools and runtime maintenance. Includes guides for the blazor-buildtools CLI (CheckNodeJsInstalledCommand and ILWipeCommand), generating the .NET WASM timezone database, and the process for upgrading Mono WebAssembly builds.
Blazor has moved from this repository to the ASP.NET Core repository. For source code, issues, and pull requests related to Blazor components, visit the ASP.NET Core repository.
Do not post new issues or pull requests in the old dotnet/blazor repository.
To build the timezone database project, you must have the following environment ready:
dotnet.timezones.dat file, which is the timezone database used by the .NET WASM runtime. Note that the output file is currently manually regenerated and must be committed to git after building.Use the provided upgrade script to replace existing binaries in the repository with the new Mono build. The script removes older binaries from the incoming and tools directories and copies the new structure from your extracted build.
From the root directory of the repository, run UpgradeMono.[cmd|ps1] followed by the path to your extracted Mono build.
Expected changes in Git diff:
dotnet.js and dotnet.wasm should be modified.bcl and bcl\facades should be modified (new or removed assemblies are rare but possible).framework should be modified (adding or removing assemblies here is unexpected and should be verified with Mono).tools should be modified.Commit Convention:
Commit the changes with a message following this pattern: Upgrade Mono binaries to <their-commit-sha>, where <their-commit-sha> is the SHA found in the downloaded Mono zip filename.
UpgradeMono.cmd C:\Users\you\Downloads\mono-wasm-a93e4712ecdAfter pushing your changes to the blazor repository, you must verify the upgrade by integrating it into the aspnetcore repository.
Microsoft.AspNetCore.Components.WebAssembly.Runtime.3.2.0-ci.nupkg), download it.aspnetcore repository, modify eng\Versions.props. Update the MicrosoftAspNetCoreComponentsWebAssemblyRuntimePackageVersion property to your new version (e.g., 3.2.0-ci).-ci version of the package exists in your local NuGet cache.dotnet restore pointing to the directory containing your downloaded package using the -s flag.StandaloneApp and performance benchmarks to ensure functionality and check for regressions in size or performance.src\Components\test\E2ETest.yarn install to install dependencies (selenium, chrome debug adapter, etc.).dotnet test via the command line or through Visual Studio.To upgrade Mono and the Mono Linker, you must first download the latest Mono WebAssembly builds from the Jenkins server.
https://jenkins.mono-project.com/job/test-mono-mainline-wasm/..zip file.Note: The filename contains the commit's SHA hash, which is required for tracking the Mono version used in Blazor.
Direct Access Shortcut:
You can browse directly to the Azure directory by replacing the build number in this URL: https://jenkins.mono-project.com/job/test-mono-mainline-wasm/<BUILD_NUMBER>/label=ubuntu-1804-amd64/Azure/.
For official documentation, guides, and information on how to use Blazor, visit the official Blazor website.
https://blazor.netThe following options are available for the ILWipeCommand:
| Option | Long Name | Description |
|---|---|---|
-i | --input | Required. The directory containing assemblies from which code should be wiped. |
-s | --spec | Required. The directory containing spec files (*.txt) describing which members to wipe. |
-o | --output | Required. The directory to which the wiped assembly files should be written. |
-v | --verbose | If set, logs additional information to the console. |
-l | --list | If set, just writes lists the assembly contents to disk instead of wiping. |
-h | --help | Displays help information. |
The blazor-buildtools CLI provides tools for Blazor build processes, including Node.js environment checks and IL Wiping.
To view the available commands and help information, run the executable with the -?, -h, or --help flag.
The CheckNodeJsInstalledCommand is a CLI utility used to assert that Node.js is installed on the system and meets a minimum version requirement. It executes node -v to detect the version and compares it against a specified threshold.
Run the command to check for Node.js. If Node.js is not found or the version is insufficient, the command will exit with code 1 and print an error message to the console.
-v|--version: Specifies a minimum acceptable version of Node.js (e.g., 14.17.0).checknodejs command verifies if Node.js is installed on the system, which is a requirement for certain Blazor build tasks.The ILWipeCommand is a CLI tool used to wipe specific code members from .NET assemblies based on specification files. It processes assemblies located in an input directory and writes the modified assemblies to an output directory.
If the --list flag is used, the tool will not perform a wipe; instead, it will list the contents of the assemblies to disk as text files in the output directory.