Adding package results in large file size?

[fredrikbaberg]

Hi,
I've just started to look at this as a solution to integrate BabylonJS in a Blazor WebAssembly project.

I noticed the output project from dotnet publish -c Release increases a lot after adding this package, where the main contributor seems to be Microsoft.CodeAnalysis at 84 files in _framework for a total of 20,2 MB.

To recreate:

dotnet new blazorwasm -o TestCodeAnalysis
cd TestCodeAnalysis
dotnet add package EventHorizon.Blazor.TypeScript.Interop.Generator
dotnet publish -c Release

The resulting publish folder increases from 14.8 MB to 41,3 MB.

Is Microsoft.CodeAnalysis required, or is this a bug?

I'm currently on .NET 6 Preview 7, so I haven't verified if this happens on 5.0 or 6 RC1 yet.

[canhorn]

The main source project is not optimized for a deployed application, it's intended to create the C# projects as part of an out of process build.
But the dependency comes from the embedded CSharp formatter, that can be used to format the generated files. It's is not necessary and I will look at moving it into a sub-project in a future release.

The Generation Tool can be used from the CLI and in the Sample directory there is an example of a Console application that uses EventHorizon.Blazor.TypeScript.Interop.Generator to create the C# project.

If you want a more flushed out example of a game that uses the Generation Tool for BabylonJS and integrates it with a Blazor Wasm application: https://github.com/canhorn/BabylonJS.Blazor.Game.Tutorial

[fredrikbaberg]

Thank you for the quick reply. I saw that repository and thought I followed it, but noticed some differences when I had another look. The resulting size is now more reasonable.