2

I need to use native C libraries in my library (that supports several Core TFs and .NET Framework) which is published via NuGet. I configured it via a .csproj file and a runtimes folder, but I noticed that when I consume my NuGet via dotnet add package ... in some cases, the native libraries are not copied into the expected folder after consuming, however when I use the Visual Studio NuGet Package Manager and select "Manage NuGet Packages for Solution", all files are placed into correct places.

So, I assume that NuGet package manager makes more steps than just calling dotnet add package ..., but it's unclear what exactly happens.

Improve this question
3
  • also, if anyone can point me out on the "complex" guide to nuget configuration (preferably via .csproj), it will be also appreciated Commented Sep 26, 2020 at 23:20
  • @PerryQian-MSFT, I double-checked this issue, it looks like I was wrong, at least I wasn't able to reproduce exactly the described issue. Most likely my problem was related to the difference in how consumer applications with csprojs in sdk style and non-sdk style are processed. Now, I see that my non-sdk project handles .net framework TF correctly (including via PM and Install-Package package way), but when I try to use .net framework in sdk style, the native library is not copied into the expected place. So, some more investigation is required here. Thanks a lot! Commented Oct 2, 2020 at 22:44
  • Runtime folder of the nuget works for new sdk style project. And it is strange why it works for non-sdk projects. You should check on this document and make sure the sructure is right. Besides, please try to use net standard library project as the nuget project. Secondly, you can use content folder or lib folder to copies files or reference dlls into your main projects. Commented Oct 5, 2020 at 6:27

1 Answer 1

Reset to default
1

Actually, dotnet add package does the same thing as the NuGet Package Manager: they both install a NuGet package into your project. No additional operations will be performed.

So I think there is something else wrong in your project.

Please check under tips to troubleshoot your issue:

  1. clean your NuGet cache first or just delete all cache files under C:\Users\xxx(current user)\.nuget\packages.

  2. If the runtimes folder does not exist under your project, I think it is controlled by dependency assets. Like ExcludeAssets=runtime or native. It will prevent the function of runtimes folder. Please see this official document.

    After you finishing installing the NuGet package, you should check your .csproj file, and make sure that there is nothing like

    <ExcludeAssets>runtime;native</ExcludeAssets>

    under the PackageReference node.

    If there is any such content under this node, please delete it.

  3. delete your bin and obj folders. Then rebuild your project to test again. Or if you use the command line, you should additionally add a dotnet build command. In my side, I run dotnet build -p:platform=xxx;Configuration=Release.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.