nuget-package

问题 I have the error from below and I'm quite out of ideas how to solve it. Tried the following until now: Clean bin/obj/packages/packages cache Remove manually from csproj and packages files the package and add it afterwards..still error Update Visual Studio 2017 Reinstall Visual Studio 2017 Trace which processes are using a file with name that contains Newtonsoft Copy the solution from another laptop where the builds works just fine Yet, after all from above, I still get: Error NuGet Package

问题 We are using our own nuget server on the local network. I've got a dotnet standard 2.0 library which I'm packaging via nuget. Currently it's at 1.0.5.4 (both File version and Assembly version). However when I install it in another solution it's missing a property that I added in the latest version increment. When I F12 on a class of that nuget it reads at the top: #region Assembly lib-mycode-async, Version=1.0.5.1, Culture=neutral, PublicKeyToken=null // C:\Users\{Username}\.nuget\packages

问题 unamanged shared object (.so file) does not copy to the output directory: I have .netstandard 2 project that wraps a c++ library(lets call the project wrap.csproj). That project depends on shared object (libgdal.so). I want to use this project as a nuget, and therefor, the projects that will reference my nuget should have the wrap.dll and the libgdal.so in the build/publish folder. I packed this project as nuget. but projects( dotnet core) that reference this nuget does not get the libgdal.so

问题 Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 2 months ago . Improve this question In v3.5 the behaviour has changed so that when it packs a package it will strip off leading zeros. This is not the behaviour we want. I hope it can be fixed in v3.6. 回答1: As explained on the Package versioning page there was a breaking change introduced for NuGet

问题 Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 2 months ago . Improve this question In v3.5 the behaviour has changed so that when it packs a package it will strip off leading zeros. This is not the behaviour we want. I hope it can be fixed in v3.6. 回答1: As explained on the Package versioning page there was a breaking change introduced for NuGet

问题 Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 2 months ago . Improve this question In v3.5 the behaviour has changed so that when it packs a package it will strip off leading zeros. This is not the behaviour we want. I hope it can be fixed in v3.6. 回答1: As explained on the Package versioning page there was a breaking change introduced for NuGet

问题 I am trying to create a nuget using the csproj file. My files are copied, but my log4net.config (and others) are treated as a link when the nuget package is imported by another project. These files are also not copied to the target directory on build. (see the blue icon in the screenshot below) My cs project contains the following code. <ItemGroup> <Content Include="contentFiles/**/*.*;log4net.config" copyToOutput="true"> <IncludeInPackage>true</IncludeInPackage> <CopyToOutput>true<

问题 I have C# project that has to target .NET 3.5. framework and I have several nuget packages I'd like to install in the given project. How to find out, for a given nuget package, which .NET framework versions it supports (by version of package for example), without me trying to install every available version of the package in order to see if its installation will pass without rolling back because of the dependency of the given version of the package to .NET framework higher than 3.5.? For

问题 I have C# project that has to target .NET 3.5. framework and I have several nuget packages I'd like to install in the given project. How to find out, for a given nuget package, which .NET framework versions it supports (by version of package for example), without me trying to install every available version of the package in order to see if its installation will pass without rolling back because of the dependency of the given version of the package to .NET framework higher than 3.5.? For

问题 I have C# project that has to target .NET 3.5. framework and I have several nuget packages I'd like to install in the given project. How to find out, for a given nuget package, which .NET framework versions it supports (by version of package for example), without me trying to install every available version of the package in order to see if its installation will pass without rolling back because of the dependency of the given version of the package to .NET framework higher than 3.5.? For