ikvm icon indicating copy to clipboard operation
ikvm copied to clipboard

Is 8.11.0 supposed to increase Nuget package size considerably?

Open martin-honnen opened this issue 10 months ago • 5 comments

I tend to build some dotnet tools with IKVM (like https://www.nuget.org/packages/SaxonHE12NetXslt/ or https://www.nuget.org/packages/SaxonHE12NetXQuery/), these were always rather bulky (some 226 MB) but below the NuGet package limit of 250 MB.

I have rebuilt a new version using IKVM 8.11.0 and find that packages are now about 295 MB, too big for NuGet.

Is there anything changed in IKVM 8.11.0 compared to IKVM 8.10.3 that increases NuGet package size that drastically?

martin-honnen avatar Feb 04 '25 17:02 martin-honnen

Hmm. There was those new android libs that aren't used for anything yet. I had not considered the scenarios where people repackage IKVM completely into a single NuGet package. Which I guess makes sense for tools. Hmmm.

wasabii avatar Feb 04 '25 17:02 wasabii

I would suggest there's really no reason to package a net9 version of the tool is there? IKVM itself doesn't even have a .NET 9 build.

wasabii avatar Feb 04 '25 17:02 wasabii

Right, let me try whether packaging for .NET 8 only gets me back below 250 MB.

martin-honnen avatar Feb 04 '25 17:02 martin-honnen

I really wish NuGet would move to a better compression format than Zip.

wasabii avatar Feb 04 '25 17:02 wasabii

By creating .NET 8 only NuGet packages I indeed got only 147 MB sized packages so I can at least continue to upload them to NuGet.

I can close this unless you want to keep it open to drop Android libs as long as they are not used yet, can't tell whether that makes any sense.

Let me know.

martin-honnen avatar Feb 04 '25 18:02 martin-honnen