Aspnetcore: Optimize the BCL

[javiercn]

The work here is to:

• [x] Setup illink on the project.
• [x] Run the linker through the app.
• [ ] Determine what references are left behind on the app and what of those things are potential candidates to strip.

[javiercn]

So far I've been able to run this on StandaloneApp and I've been able to trim the BCL to

The command that i've used is

illink.exe -a .\Microsoft.AspNetCore.Blazor.Browser.dll \
 -a .\Microsoft.AspNetCore.Blazor.dll -a .\StandaloneApp.dll \
-d .\dist\_framework\_bin\ -c link -out .\optimized --skip-unresolved true

mscorlib is by a large margin the biggest assembly here. Zipping the remaining files leaves them at around 590K

Above is the remaining namespaces left on the assembly.

The next step is to determine what of those things can go away and see how much we save.

[grahamehorner]

@javiercn IMHO anything that would in essence be anything that would break outside the browser sandbox? things like Win32, file IO etc. these could be placed with interop with browser APIs which could save quite a bit of space ;)

loving the work on this now it's an official project of research; can't wait to see what the teams direction is on the feature roadmap @SteveSandersonMS +1

[javiercn]

Done 59635331601dc8496c7cd5958552dec24d1b0ffd.
https://github.com/aspnet/Blazor/issues/245 Tracks further improvements