-
-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is 8.11.0 supposed to increase Nuget package size considerably? #658
Comments
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. |
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. |
Right, let me try whether packaging for .NET 8 only gets me back below 250 MB. |
I really wish NuGet would move to a better compression format than Zip. |
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. |
I tend to build some
dotnet tool
s 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?
The text was updated successfully, but these errors were encountered: