![]() This might help you identify what is taking the longest and it may potentially be a step you can disable. The log viewer should show all the msbuild tasks executed by the publish and their durations. You can produce a binlog for your publish and analyze it using MSBuild Log Viewer. See How to get MSBuild binlogs using command line. If you really want to determine which part of the build is taking the most time I would recommend generating a binlog of the publish and reviewing it to see which msbuild tasks are taking the longest. Ahead of Time Compilation (AOT) - If this is enabled then the build times will be significantly higher as your trimmed assemblies will be compiled directly to wasm.Compression - The publish will compress all of the resources (dll's, static assets, etc) to ensure efficient transfer over the wire.IL Trimming - Publish will strip all unreferenced code from the assemblies to reduce the application size. ![]() Here are a few steps are done in a publish which are expensive and can add significantly to the build time. Without out seeing your project file its hard to determine exactly why things are taking so long. There are several steps involved in a blazor wasm publish that do not happen when you are just debugging or running Blazor WASM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |