The Packager command line in the ShellTask miss some assemblies about uno.wasm.bootstrap HOT 5 CLOSED

thank you so much for your time Jerome.

from uno.wasm.bootstrap.

@jeromelaban i think it's a bug, if i understand the whole chain, i don't want the packager miss some assemblies, I expect to have all after him and use the linker to "clear" them.
It's a complex chain, i don't say i'm right, but i hope you have an opinion about that :-)

from uno.wasm.bootstrap.

Thanks for the report!

Reference assemblies cannot be part of the dist layout, as the runtime cannot load them properly (they're empty).

How did you find out this can be an issue ?

from uno.wasm.bootstrap.

oh you right, i make a mistake ... forget my workaround :)

i begin to understand. dotnet.wasm already contains assemblies. I have to work to understand more this architecture :)

If you want to understand the context, i am porting PowerShell to WASM
https://fmichaleczek.github.io/PowerShellLab/

Enter this code :

[AppDomain]::CurrentDomain.GetAssemblies() | Select FullName
Add-Type -AssemblyName Microsoft.PowerShell.ConsoleHost -PassThru

You will see I load assembly on demand ...

It's to make a playground for PowerShell because we have nothing and nobody want to host one :)

from uno.wasm.bootstrap.

Just saw your post on twitter! Very cool demo !

As for that assembly, it's actually included in the System.Xml file if I'm not mistaken (all the extensions provided by System.Xml.XmlDocument).

Also in the configuration you're using, the dotnet.wasm file only contains native code as the .dll files are interpreted.

from uno.wasm.bootstrap.