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
System packages when installing on .NET Core 3.0 #140
Comments
Well.. It seems that everything listed above is more or less needed within RT, yes :) |
@pavel-b-novikov - Shouldn't it just be using the system packages though? I don't understand why it had to install them from NuGet. This part in particular looks suspicious:
Why is it referencing Microsoft.NETCore.App 2.0 in my 3.0 app? |
RT is multi-targeting, so it has versions for netcoreapp2.0, full-sized .NET and other verions. I'm not sure, but suspect that it is somehow related. Anyway it seems that I do not list anything critical with nuspec. I'm trying to keep RT as small as possible, but maybe you can help to find out what problem is there? |
I'll try to take a look soon! |
Filed in NuGet repo too: NuGet/Home#8734 |
Thanks a lot! I have too much activity to take a look on this |
Hi! I see this in my NETCoreApp 3.0 project too, even when using Paket instead of NuGet, For the published version 1.5.5, it results in the netcoreapp2.0 dependencies being required for netcoreapp3.0 project, instead of any netstandard version, as any netcoreapp is "closer" than any netstandard, regardless of version. In this case, the fix should be adding a netcoreapp3.0 section in the NuGet/NuSpec, with the same dependencies as netstandard2.0, to prevent the fallback to older netcoreapp. |
I will try, thanks |
@pavel-b-novikov after digging a bit deeper, it even seems like both of the netstandard2.0 dependencies are part of the now implicit and hidden Microsoft.NETCore.App/3.0.0, so the netcoreapp3.0 dependencies section should be present and empty, I'd believe. |
I got this reply from the NuGet team:
I guess my testing wasn't actually effective as it was using a cached version of the package. @viktor-svub Have you attempted to fix it? |
… to the nuspec, avoiding unexpected fallback paths
ok, after a slightly longer delay than expected, I got to build the nuget locally and verified the assumed fix, here is the PR #155 :) |
fixes issue #140 by adding netcoreapp3.0 and 3.1 explicitly
When I install this in a .NET Core 3.0 app, it seems to pull a whole heap of packages from NuGet:
Is this expected?
The text was updated successfully, but these errors were encountered: