nuget-package

问题 My Build and Deploy step in TeamCity is not successfully executed. It is showing "This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\Microsoft.Net.Compilers.1.0.0\build\Microsoft.Net.Compilers.props." Below is the step process log: [Step 1/1] WebApplication2.sln.teamcity: Build target: TeamCity_Generated_Build [22:31:54]

问题 I have my Nuget library uploaded into Azure Devops Artifacts. It also has the Symbols file (.PDB) published to the Azure Devops symbols server. I have added settings in my Visual studio to load symbols from the Azure Devops Symbols server as well by following the instructions mentioned here. During the runtime, when I try to StepInto the code (of Nuget library) then I get error saying unable to find the path of the .cs file. I have tried various solutions proposed like Uncheck the Enable Just

问题 I am working with a solution in visual studio that has multiple projects in it. One area of the project requires RestSharp 106.10.1, and in another project (that it needs to talk to) we have the Docuign.ESign.dll that has RestSharp 106.3.1 as an interior dependency. When trying to run the project with the Docusing dll, we get a run time error of "Could not load file or assembly 'RestSharp, Version=106.3.1.0, Culture=neutral, PublicKeyToken=598062e77f915f75'. The system cannot find the file

问题 I have a build pipeline set up to create Nuget packages and publish them to a feed in artifacts. I was able to use the feed successfully. However when I ran the pipeline again, causing the packages to publish again I am not able to update the consuming project successfully. Even though I can see the correct new version number in the Package Manager (Visual Studio -> Tools-> Nuget Package Manager -> Manage Nuget Packages for solution) When I click install I get an error Package '<mypackagename

问题 I recently upgraded from ASP.NET Core 2.2. to 3.0. With the changes regarding their meta packages, I'm now in a state where everything works, but some pretty important packages are not explicitly referenced. Everything works because, they're implicitly referenced. For example: You can see that I'm explicitly referencing Microsoft.EntityFrameworkCore.SqlServer, however I am NOT referencing Microsoft.EntityFrameworkCore explicitly. It's still pulled in because it's an indirect reference it

问题 I recently upgraded from ASP.NET Core 2.2. to 3.0. With the changes regarding their meta packages, I'm now in a state where everything works, but some pretty important packages are not explicitly referenced. Everything works because, they're implicitly referenced. For example: You can see that I'm explicitly referencing Microsoft.EntityFrameworkCore.SqlServer, however I am NOT referencing Microsoft.EntityFrameworkCore explicitly. It's still pulled in because it's an indirect reference it

问题 I'm developing an Nuget Package. I have icon.png placed inside Images folder inside my package code. In my .csproj file I have added required tags related to icon. But still icon is not getting displayed. Instead default blue icon is displayed in Nuget. Here is my .csproj file, <PropertyGroup> <PackageIcon>icon.png</PackageIcon> </PropertyGroup> <ItemGroup> <None Include="Images\icon.png" Pack="true" PackagePath=""/> </ItemGroup> Am I missing anything? please assist. 回答1: Currently,

问题 I used Fody Nuget package as follows Install package PM> Install-Package MethodDecorator.Fody Decorate the method public class BusinessLayerClass { [LogMethod] public string BusinessLayerMethod() { DataLayerClass dataLayerClass = new DataLayerClass(); return dataLayerClass.DataLayerMethod(); } } Write the interceptor using System; using System.Reflection; [module: LogMethod] // Attribute should be "registered" by adding as module or assembly custom attribute // Any attribute which provides

问题 Is it true that for every dependency that a package has on some other library, that those libraries need to be resolved and installed as well? For example, I created a package which uses NLog , Postsharp and WindowsAzure.Storage : Do clients of my package now have to install these packages as well? Why is it not possible to include these dependency DLLs within the package? 回答1: When a consumer installs your nuget package, nuget will automatically resolve and install the dependent packages as

问题 When we create a nuget package in visual studio 2017, it adds the project references as another nuget reference by default. How can we disable that while creating package and instead: Chose a different package name include the dll of the project instead while creating the package 回答1: The PackageReference can be marked with PrivateAssets="All" to ensure that it doesn't end up as a NuGet dependency of the consuming library when packed. Then the consuming library can use a custom target to add