Reduce the binary size of the single file publish of .net core WPF

I know there is some kind of long term planning of WPF with dot core. But a common scenario of x copy deployment independent of OS framework setup so called 'self-contained' is NOT acceptable due to its huge size.
Look, I created my first GITHUB release of WPF App here:
[WPF-GO-dnscrypt-proxy-md](https://github.com/AZ-X/WPF-GO-dnscrypt-proxy-md)
The release zip package can be downloaded:
[WPF-dnscrypt-proxy-md-single-binary-release-can-run-without-dotnet-framework.zip](https://github.com/AZ-X/WPF-GO-dnscrypt-proxy-md/releases/download/latest/WPF-dnscrypt-proxy-md-single-binary-release-can-run-without-dotnet-framework.zip)
It’s up to 43M while the size of an extracted single exe file is 150M.
The application is a single windows form. Looks like:
Please improve ~~this issue~~ the total of size and institute a spec of various release sizes as soon as possible, even I don’t have a deadline for it. Please make WPF great again.

----------------------------------------------------------------------------------------------------------

A reference for contrast:
[stammel_go.dll](https://github.com/AZ-X/WPF-GO-dnscrypt-proxy-md/blob/master/stammel_go.dll)

A go library built inside this project which size is about 2.5M including go framework. I know the size issue could not be resolved as just involving WPF, but it is an obvious spot if a real application builder would be encountering the same issue with the same feeling.