Dear Sir/Madam,
I'm afraid somerhing is not quite right with our ABP solution - Blazor WebAssembly front-end project to be exact (we just started with our Blazor front-end project and it contains < 20 components).
We're on v4.3.3 (.NET core v5.0.301) and most of us in the dev team are experiencing slow build times ( ~3 minutes). So far, I've tried to reinstall Visual Studio 2019 Enterprise (v16.10.2) and I've switched to another PC (new hardware, 6 core CPU, 32GB RAM, NVMe SSD).
While building, I can see VBSCCompiler and CSC exe files take 10-25% of the CPU. Web API project is OK (builds in <10 seconds), but our front-end project is really troubling us. I tried to build a different solution, without ABP, and it took only a few seconds. I cloned this project https://github.com/syncfusion/blazor-samples and dotnet build took ~15 seconds.
Is anyone else experiencing similar issues? Do you have any suggestions that might help us?
Best Regards, Miroslav Šturlan Teched Ltd.
6 Answer(s)
-
0
Hi Miroslov,
thanks for the feedback. to filter down the problem, download a brand new ABP project and test the durations again
-
0
Hi,
I tried the EasyCRM application and it tooks ~12 seconds to build for me. Can you download and try to build it: https://docs.abp.io/en/commercial/latest/samples/easy-crm First build may take more time since it will restore the packages. But, after that, change a .cs file in the Blazor application and try building the solution again (F6). This application contains 20+ components/pages, so it is a good reference. Please try it and share the results. Thanks.
-
0
Hi,
I tried your application and can confirm that build time is <15 seconds after changing one .razor file. But, I noticed this project is locked to .NET v5.0.100 and we are on the latest version (5.0.301). Could this somehow impact our build time?
-
0
Hi,
I tried with 5.0.301 (you can also try this), but the result is same, no problem. This is probably not ABP-related. 3 minutes is really an extraordinary situation and that might be related to something specific to your solution. If you can try some changes (like trying to get an older version from your source control to understand when that happended - if the problem arised recently) to understand the specific point of the issue, we can help you more.
-
0
Hi,
We managed to identify the problem, it seems. Obviously everything slowed down when our component topped 800 lines of code. But, even if we don't introduce such components, visual studio is a bit laggy, but we can live with that.
Thanks for the support, if anything else comes up, we'll reach out to you.
Best Regards, Miroslav
-
0
thanks for the feedback
