Self-contained deployment not working? - MonoGame w/ NetBeauty

[lunkums]

Howdy,

I'm trying to deploy my MonoGame project as a standalone application with Netbeauty. I run the following command in the .NET CLI:

dotnet publish -c Release -r win-x64 /p:PublishReadyToRun=false /p:TieredCompilation=false --self-contained

When I have:

<DisableBeauty>True</DisableBeauty>

in my .csproj file, the deployed application is ~ 145mb. When I have:

<DisableBeauty>False</DisableBeauty>

in my .csproj file, the deployed application is ~70mb. This leads me to believe NetBeauty is excluding the .NET runtime from the deployment. Here are the contents of my .csproj file: https://pastebin.com/xRp8XzVr

Is it true that NetBeauty is excluding the .NET runtime from my deployed game, or is it automatically cleaning up unused files?

Thanks,
Luke

[liesauer]

no, NetBeauty doesn't remove any references. it's kind of weird. can i get the both copies of the deployed application with beauty enable and beauty diable? the files structure is ok too(you can get the structure with tree command), but it's better that have the application copies for furture testing.

[lunkums]

Yup, here's the two deployed applications as .zip files: https://drive.google.com/drive/folders/1MzLVi_9BDv3oGNMzI9Xr6bwC95XX3zIw?usp=sharing

And here's the project itself on GitHub: https://github.com/lunkums/LD51

[liesauer]

i found out what happened.
the first time you published the application with NetBeauty enable, all the assemblies have been move to libraries which is expected.
the second time you published the application with NetBeauty disable, msbuild doesn't clean up the publish folder and leaves the old libraries in there, that is why you get double size of the assemblies.

[liesauer]

you should clean up the publish folder when switching the config by simply delete it.

[lunkums]

doh. You're right. I usually do this, but I think I was in a rush and figured there was some other problem. Thank you for your help :)

[liesauer]

it's glad that help.