I have a CI/CD Pipeline that builds a .NET Core Solution, containing multiple Class Library Projects, to build NuGet Packages. These NuGet packages are stored in a Feed in Azure Artifacts. Works fine.

But somehow there are a lot of other packages stored in there, which are not from me or from the pipeline? NuGet Packages from different repos (CsvHelper, Azure.Identity,...)

How is that possible?

After a couple of weeks I revisited my .NET C# project in Visual Studio 2010. I changed just one line in source code and tried to rebuild the project and I get this error:

Error occurred while restoring NuGet packages: could not be found. (Exception from HRESULT: 0x80030002 (STG_E_FILENOTFOUND))

I don't have the slightest clue why this error appeared. Nothing was changed, somehow this nuget got corrupted.I have done a lot of searching via google but found nothing that would get me on the right track.

is it possible to remove nuget all together, because it is nothing but a cause of grief?

I have a .Net Core repo, that consists of various smaller projects, and a pipeline that builds it, tests it, and publishes the nugets on the feed.My problem is that all different nugets that get published have the same version.

What I want to accomplish is to have for each nuget published a different version according to how it is developed/pushed (I cannot just split the repo). Is this possible?

I am attempting to publish and consume versioned NuGet packages of class libraries while avoiding headaches for local development. Here is a sample Visual Studio solution layout:

| Libraries  | LibraryA  | LibraryB  | LibraryC| Applications  | ApplicationD  | ApplicationE

This is a single solution containing both shared class libraries and multiple applications. Currently references to the class libraries by the applications are local in-solution references.

What I would like to do is to publish the libraries (A,B,C) as versioned NuGet packages which are then referenced by the applications as needed (D,E). This allows a change to a shared library to be independent from an update to an application which is deployed. Without this, changing one library could cause the binaries to change in a dozen or more applications, all of which would technically need to be tested. This is undesirable, and versioning with NuGet fixes this.

However, let us say that I want to update the content of LibraryA and ApplicationD at the same time. In order to do this after we have switched to NuGet, I will have to make changes to LibraryA, commit them, wait for the package to be created, tell ApplicationD to update its reference to LibraryA, and then test or develop in ApplicationD. This is far more complicated than simply working with both at the same time using local in-solution references.

What is a better way to get both the robustness of versioned NuGet packages for my shared class libraries while also keeping development simple even if it spans over multiple projects and applications? The only other solutions I have found all involve too much overhead or headache, such as having to constantly change the references for ApplicationD between the NuGet package and the local project.

EDIT: To clarify the premise, this question assumes the following:

• The architecture (solution and project organization) cannot be significantly reorganized
• Shared libraries are going to change at a non-trivial frequency
• Changing a shared library cannot force any application to be updated
• Applications can reference different versions of shared libraries

I'm currently working on a YAML pipeline in Azure pipelines and have run into a snag. I already have a work around; however, I was curious if anyone has encountered this and solved for it properly. Here is the issue.

I have a project that contains multiple solutions. Some solutions are utilizing package.config and others are using PackageReference. This wasn't really a big deal until we got to performing a nuget restore on the solutions within the project using the task below.

- task: NuGetToolInstaller@1  displayName: 'Detect\Install NuGet'- task: NuGetCommand@2  displayName: 'Restore NuGet Packages'  inputs:    restoreSolution: '**\*.sln'    feedsToUse: 'config'    command: 'restore'

The tasks above successfully detect an existing NuGet installation, if not it install the latest version of NuGet. Then it performs a nuget restore of all packages using PackageReference. This is where the rub comes into play. Any solutions that are utilizing package.config are skipped by this task since it defaults to the PackageReference solutions. To get around this issue we have added an additional NuGet command task that we point to a local nuget.config file within our repository.

Note: The first task utilizes the system default nuget.config file configured on our pipeline agents.

- task: NuGetCommand@2  displayName: 'Restore NuGet Packages for package.config'  inputs:    restoreSolution: '**\*.sln'    feedsToUse: 'config'    nugetConfigPath: 'nuget.config'

While this isn't adding a large amount of time to your builds, it still isn't ideal as it would be nice to utilize a single task. Any help would be greatly appreciated.

Thanks,Source Code

I've been tackling some odd behaviour I have with my Visual Studio. I am generating pakage with simple Silo.Configuration namespace in it having two types in one file.

1. Contents of the file:

namespace Silo.Configuration{    public enum ClusteringType    {        Local,        Zookeeper    }    public class SiloConfig    {        public string URL { get; set; }        public string ClusterId { get; set; }        public string ServiceId { get; set; }        public ClusteringType ClusteringType { get; set; }        public int GatewayPort { get; set; }        public int SiloPort { get; set; }    }}

2. Silo.Configuration is the default namespace and assembly name for the package I create via Visual Studio with <GeneratePackageOnBuild>true</GeneratePackageOnBuild> option.

So far so good, but when I try to use this package in other project nested inside other namespace I get CS0234. Weird thing comes when I move Silo.Configuration in global namespace or add using global:: this fixes the error and type is resolved.

Question is what is this behaviour and how can I fix it? Before you answer I noticed when I was able to resolve SiloConfig from the other project I wanted it to be included it was looking like that

using Silo.Configuration; // <-- notice this?namespace Silo.Configuration{    public class SiloConfig    {        public SiloConfig();        public string URL { get; set; }        public string ClusterId { get; set; }        public string ServiceId { get; set; }        public ClusteringType ClusteringType { get; set; }        public int GatewayPort { get; set; }        public int SiloPort { get; set; }    }}

What does generate this using above the SiloConfig type if the namespace is the same?

I want to install phantomJS nuget package for my .NET Core project. This nuget package contains an .exe file (phantomjs.exe).(C:\Users\.nuget\packages\PhantomJS\2.1.1\tools\phantomjs)

Building or publishing solution doesn't copy .exe file inside the bin or publish folder.

Do I have to add a specific configuration in my project.json to automatically copy .exe when I'll publish or build??

I have a requirement to create different type of NuGet with Same project. I know we can create different nuspec file for this purpose. I just wanted to know if it is possible to create a parent nuspec file with common content and use it in child nuspec file.

I wanted to do this so that nuspec file mangement would be easy.

Thanks

I am new to learning C# and whenever I try to add a package in I receive this error message:

Could not find any project in C:\Users\Brian\Desktop\CFBSharp-master\.

Let's say i have a windows forms application with a few Nuget packages that are important and need to be kept up-to date.

Is it somehow possible to update Nuget packages programatically from a non-development environment? With a non-development environment i mean a random user that is running the winforms application (having it installed on their pc)

I've read some things about using nuget.exe, but updating the nuget packages should result in .dll files to be placed in the installation folder

In my Azure DevOps Build pipeline, I have added a NuGet task of pack command type (version 2.*).

I am trying to pass the -Exclude ***.tt argument so that it excludes these files when referenced from another projects. However, in the generated NuGet package, those .tt files are appearing in the Content folder.

The command written in the log of the host is:

nuget.exe pack PROJECTNAME.csproj -NonInteractive -OutputDirectory SOME_OUTPUTPATH -Properties "Configuration=release;\"-Exclude ***.tt\"" -Verbosity Detailed

As you see, exclude is not part of the properties but should be as a separate -Exclude argument.

Any idea how may I achieve this? Many thanks!

Added a screenshot and YAML:

steps:- task: NuGetCommand@2  displayName: 'NuGet pack'  inputs:    command: pack    packagesToPack: ProjectName.csproj    buildProperties: '-Exclude ***.tt'

Process:

1. Create a NuGet package called FooPackage. The package consists of two DLLs: BarDLL is a C# wrapper, BazDLL is an F# library which defines a type called QuxType. The package and the DLLs it contains are all version 1.0.0.
2. Publish the package to our private NuGet host.
3. Install FooPackage in solution CorgeSolution and reference QuxTpe.
4. Remove QuxType from FooPackage and replaced it with QuuxType, meanwhile updating the package and the DLLs to version 2.0.0
5. Update the package in CorgeSolution without removing the reference to QuxType.

Expected result: compile error in CorgeSolution. Since the type is no longer included in the installed package, it should not be possible to reference it.

Actual result: no compile error.

Other details

Using ReSharper I can navigate to a decompiled version of QuxType. There, I find the DLL version number is reported as 1.0.0, and a folder reference is given. I can delete the folder containing V1.0.0, but NuGet restores it in the blink of an eye.

Question

What's going on here? Why is the deprecated type still available?

I have a C# project that uses PackageReference to manage dependencies using NuGet. I am able to install top-level packages using the NuGet manager with no issues. However, I am looking for a way to force Nuget to install a specific version of one of the dependencies.

For example, I have a project called MainProject.Data.. In this project, I installed a package called XYZ.Main. But, XYZ.Main package has XYZ.Secondary >= 2.1.0 listed as dependency. I want a way to be able to force Nuget to install XYZ.Secondary 2.1.5, not the latest which is XYZ.Secondary 2.1.25

How can I control which dependency to install?

I am trying to install LinphoneSDK using nuget at VS2017. While installing I am getting below error :

Severity Code Description Project File Line Suppression StateError Could not install package 'LinphoneSDK 3.12.0.273'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.5', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author. 0

Any pointer how to install linphone SDK by using nuget at VS 2017? Please advice

hopefully this is not a duplicate but I didn't find or catch the solution to my problem in the other posts.

I have a project that I'm building with dotnet build -c Release /p:Platform=x86 .\Foo.csproj.The csproj file is in SDK format and have this content:

<?xml version="1.0" encoding="utf-8"?><Project Sdk="Microsoft.NET.Sdk.WindowsDesktop"><PropertyGroup><TargetFramework>net48</TargetFramework><GeneratePackageOnBuild>true</GeneratePackageOnBuild><AssemblyName>Foo</AssemblyName><Company>Me</Company><Authors>Me</Authors><Version>4.12.5</Version><AssemblyVersion>4.12.5.0</AssemblyVersion><FileVersion>4.12.5.0</FileVersion><Platforms>x86</Platforms><UseWPF>true</UseWPF></PropertyGroup><ItemGroup><ProjectReference Include="..\Bar.csproj">[...]</ProjectReference></ItemGroup><ItemGroup Label="FilesToCopy"><Content Include="..\dependent.dll" Pack="true" PackagePath=".\lib\net48\" PackageCopyToOutput="true" /><None Include="image.jpg" Pack="true" PackagePath=".\contentFiles\any\any\" PackageCopyToOutput="true" /></ItemGroup><ItemGroup><None Update="tex_cardboard.jpg"><CopyToOutputDirectory>Always</CopyToOutputDirectory></None></ItemGroup><PropertyGroup><TargetsForTfmSpecificBuildOutput>$(TargetsForTfmSpecificBuildOutput);CopyProjectReferencesToPackage</TargetsForTfmSpecificBuildOutput></PropertyGroup><Target Name="CopyProjectReferencesToPackage" DependsOnTargets="ResolveReferences"><ItemGroup><BuildOutputInPackage Include="@(ReferenceCopyLocalPaths-&gt;WithMetadataValue('ReferenceSourceTarget', 'ProjectReference'))" /></ItemGroup></Target></Project>

This will generate a nuget package on build with the image.jpg in a contentFiles\any\any folder.

If I understand correctly, the the .nuspec file inside of the nuget package should contain:

<contentFiles><files include="**/*" buildAction="Content" /></contentFiles>

But it does not.

How do I tell, in the csproj file, the image file to be included as content and not to be compiled?

Hi) Im trying to translate our Android Native Java Library which uses Fotoapparat Library and Tensorflow Lite to Xamarin Java Binding Library. Building it from AAR with "LibraryProjectZip" build option.

Xamarin documentation ( https://docs.microsoft.com/en-us/xamarin/android/platform/binding-java-library/?WT.mc_id=xamarin-c9-jamont ) says that Java Binding Library needs its' dependencies as ReferenceJar or EmbeddedReferenceJar. It is very hard to translate big libraries like Fotoapparat and TF to xamarin library by yourself so need to use ready solutions for them.

There are xamarin nuget packages (https://www.nuget.org/packages/Karamunting.Android.RedApparat.Fotoapparat/ , https://www.nuget.org/packages/Xamarin.TensorFlow.Lite ) for those libs and I wonder if there is any way to use them as dependency for our binding library.

Also found binding for TF library (https://github.com/moljac/Xamarin.TensorFlow.Lite) and also wonder if it can be used as dependency for our binding library.

Im sorry if the question has bad format or is unclear. Im very new to xamarin, binding libraries and nuget.

I have a project which I create a nuget from. In that project I have a .txt file set as content and copy always.

when I then in an other solution install that nuget in a class library (visual studio c#), the .txt shows up in the project but is set to content and do not copy.

how can I get the default value to be copy always?

(my goal is to be able to just run that solution and get everything in it in the bin folder)

I have tried in my .nuspec to add:

<contentFiles><files include="*.txt" buildAction="Content" copyToOutput="true" flatten="true"/></contentFiles>

it doesn't seem to work

On building the project I am getting this error.

Error NETSDK1004 Assets file'J:\Test\core\fx-core\obj\project.assets.json' not found. Run a NuGetpackage restore to generate this file. FxCore C:\ProgramFiles\dotnet\sdk\3.1.201\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets 234

So to solve this I am running the command dotnet restore in package manager console. But on running I'm getting the below error.

PM> dotnet restore J:\Test\core\fx-core\FxCore.csproj(3,3): warningMSB4011: "C:\ProgramFiles\dotnet\sdk\3.1.201\Current\Microsoft.Common.props" cannot beimported again. It was already imported at "C:\ProgramFiles\dotnet\sdk\3.1.201\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.props (40,3)".This is most likely a build authoring error. This subsequent importwill be ignored. C:\ProgramFiles\dotnet\sdk\3.1.201\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.targets(37,3):warning MSB4011: "C:\ProgramFiles\dotnet\sdk\3.1.201\Microsoft.CSharp.targets" cannot be importedagain. It was already imported at "J:\Test\core\fx-core\FxCore.csproj(118,3)". This is most likely a build authoring error. This subsequentimport will be ignored. C:\ProgramFiles\dotnet\sdk\3.1.201\NuGet.targets(124,5): error : Value cannot benull. (Parameter 'folderName') [J:\Test\core\fx-core\FxCore.sln] PM>

How to solve this issue?

.Net Target framework: 4.6.1

Visual Studio: 2019 (16.5.2)

Project Type : Class library

Update:

Adding csproj file based on @Lennart request

<?xml version="1.0" encoding="utf-8"?><Project ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" Sdk="Microsoft.NET.Sdk"><Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" Condition="Exists('$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props')" /><PropertyGroup><Configuration Condition=" '$(Configuration)' == ''">Debug</Configuration><Platform Condition=" '$(Platform)' == ''">AnyCPU</Platform><ProjectGuid>{459BF9F7-69C7-4BBD-B566-CEFB992F88D5}</ProjectGuid><OutputType>Library</OutputType><AppDesignerFolder>Properties</AppDesignerFolder><RootNamespace>FX.Core</RootNamespace><AssemblyName>FxCore</AssemblyName><TargetFrameworkVersion>v4.6.1</TargetFrameworkVersion><FileAlignment>512</FileAlignment><TargetFrameworkProfile /><GeneratePackageOnBuild>true</GeneratePackageOnBuild><Version>1.0.2.9</Version><Company>INTL FCStone</Company><Authors>INTL FCStone</Authors><Description>FxCore Assembly</Description><Copyright>Copyright 2018</Copyright><PackageReleaseNotes>version 1.0.2</PackageReleaseNotes><TargetFrameworkIdentifier>.NETFramework</TargetFrameworkIdentifier></PropertyGroup><PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU'"><DebugSymbols>true</DebugSymbols><DebugType>full</DebugType><Optimize>false</Optimize><OutputPath>bin\Debug\</OutputPath><DefineConstants>TRACE;DEBUG</DefineConstants><ErrorReport>prompt</ErrorReport><WarningLevel>4</WarningLevel></PropertyGroup><PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU'"><DebugType>pdbonly</DebugType><Optimize>true</Optimize><OutputPath>bin\Release\</OutputPath><DefineConstants>TRACE</DefineConstants><ErrorReport>prompt</ErrorReport><WarningLevel>4</WarningLevel></PropertyGroup><ItemGroup><Compile Remove="packages\**" /><Compile Remove="_CreateNewNuGetPackage\**" /><EmbeddedResource Remove="packages\**" /><EmbeddedResource Remove="_CreateNewNuGetPackage\**" /><None Remove="packages\**" /><None Remove="_CreateNewNuGetPackage\**" /></ItemGroup><ItemGroup><Reference Include="Dapper, Version=1.50.2.0, Culture=neutral, processorArchitecture=MSIL"><HintPath>packages\Dapper.1.50.2\lib\net45\Dapper.dll</HintPath></Reference><Reference Include="EasyNetQ, Version=0.63.6.463, Culture=neutral, processorArchitecture=MSIL"><HintPath>packages\EasyNetQ.0.63.6.463\lib\net45\EasyNetQ.dll</HintPath></Reference><Reference Include="FXEntity, Version=1.0.1.12, Culture=neutral, processorArchitecture=MSIL"><HintPath>packages\FXEntity.1.0.2.12\lib\net45\FXEntity.dll</HintPath></Reference><Reference Include="log4net, Version=2.0.8.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a, processorArchitecture=MSIL"><HintPath>packages\log4net.2.0.8\lib\net45-full\log4net.dll</HintPath></Reference><Reference Include="Microsoft.Practices.ServiceLocation, Version=1.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL"><HintPath>packages\CommonServiceLocator.1.3\lib\portable-net4+sl5+netcore45+wpa81+wp8\Microsoft.Practices.ServiceLocation.dll</HintPath></Reference><Reference Include="Microsoft.Practices.Unity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=6d32ff45e0ccc69f, processorArchitecture=MSIL"><HintPath>packages\Unity.4.0.1\lib\net45\Microsoft.Practices.Unity.dll</HintPath></Reference><Reference Include="Microsoft.Practices.Unity.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=6d32ff45e0ccc69f, processorArchitecture=MSIL"><HintPath>packages\Unity.4.0.1\lib\net45\Microsoft.Practices.Unity.Configuration.dll</HintPath></Reference><Reference Include="Microsoft.Practices.Unity.RegistrationByConvention, Version=4.0.0.0, Culture=neutral, PublicKeyToken=6d32ff45e0ccc69f, processorArchitecture=MSIL"><HintPath>packages\Unity.4.0.1\lib\net45\Microsoft.Practices.Unity.RegistrationByConvention.dll</HintPath></Reference><Reference Include="Ninject, Version=3.2.0.0, Culture=neutral, PublicKeyToken=c7192dc5380945e7, processorArchitecture=MSIL"><HintPath>packages\Ninject.3.2.2.0\lib\net45-full\Ninject.dll</HintPath></Reference><Reference Include="RabbitMQ.Client, Version=3.6.6.0, Culture=neutral, PublicKeyToken=89e7d7c5feba84ce, processorArchitecture=MSIL"><HintPath>packages\RabbitMQ.Client.3.6.6\lib\net45\RabbitMQ.Client.dll</HintPath></Reference><Reference Include="System" /><Reference Include="System.configuration" /><Reference Include="System.Core" /><Reference Include="System.Web" /><Reference Include="System.Xml.Linq" /><Reference Include="Microsoft.CSharp" /><Reference Include="System.Data" /><Reference Include="System.Net.Http" /><Reference Include="System.Xml" /></ItemGroup><ItemGroup><Folder Include="Properties\" /><Compile Remove="Configuration\UspHostLoginValidateResult.cs" /><Compile Remove="Configuration\UspHostUserRoleMenuListResult.cs" /><Compile Remove="Properties\AssemblyInfo.cs" /><Folder Include="DataAccess\" /><Folder Include="DataAccess\Components" /><Folder Include="Diagnostics\" /><Folder Include="Diagnostics\Components" /><Folder Include="NetworkProtocols\" /><Folder Include="Unity\" />   </ItemGroup><ItemGroup><None Include="app.config"><SubType>Designer</SubType></None><None Include="packages.config" /></ItemGroup><ItemGroup><PackageReference Include="Connect.SSO" Version="3.5.6.1" /><PackageReference Include="Microsoft.AspNet.Mvc" Version="5.2.6" /><PackageReference Include="Dapper" Version="1.50.2.0" /><PackageReference Include="EasyNetQ" Version="0.63.6.463" /><PackageReference Include="log4net" Version="2.0.8.0" /><PackageReference Include="Microsoft.Practices.ServiceLocation" Version="1.3.0.0" /><PackageReference Include="Ninject" Version="3.2.0.0" /><PackageReference Include="RabbitMQ.Client" Version="3.6.6.0" /></ItemGroup><Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" /><!--<Target Name="PreBuild" BeforeTargets="PreBuildEvent"><Exec Command="&#xD;&#xA;&#xD;&#xA;&#xD;&#xA;" /></Target>--></Project>

I am getting the following Error when trying to Scaffold-DBContext. I have installed the Packages EntityFrameworkCore, Core.Design, SqlServer.Design, Core.Tools. The command I am running is.

Scaffold-DbContext "Data Source=.;Database=StudentApp;Trusted_Connection=True;" Microsoft.EntityFrameworkCore.SqlServer -OutputDir Models

The Error message I am getting is

You cannot call a method on a null-valued expression.At line:1 char:1Scaffold-DbContext "Data Source=.;Database=StudentApp

CategoryInfo : InvalidOperation: (:) [Scaffold-DbContext], RuntimeException

FullyQualifiedErrorId : InvokeMethodOnNull,Scaffold-DbContext

I am not sure what to try. I have used the ASP.Net Angula App template when creating this solution. Any help would be appreciated.

In my solution I have a few projects, which pack their own nuget packages on build. When packing the package I use the PackageID parameter to add a customprefix to the package name (which otherwise would be the name of the project).

dotnet pack  .\$(ProjectName).csproj  --include-symbols --no-build -o C:\dev\Packages -p:PackageID=CustomPrefix.$(ProjectName)

It works fine.

Now, in my Azure Devop Pipeline, I was using the dotnet task to pack my packages like so:

- task: DotNetCoreCLI@2  displayName: 'dotnet pack'  inputs:    command: 'pack'    packagesToPack: '${{parameters.solutionPath}}'    nobuild: true    includesymbols: true    versioningScheme: 'off'

Now obviously this does not add the prefix and I have no idea how to do it, especially since here I path the path to the actual solution, not the project. It just pack the packages for all projects in the solution, without any means to customize it. Any clue on how I could do that ?