Skip to main content

.NET Core - The nuget command failed with exit code(1) and error(System.InvalidCastException: Unable to cast object of type 'System.String' to type 'NuGet.Frameworks.NuGetFramework'.

After creating a .NET Core application, I configured our build pipeline to Restore the NuGet packages, Build the application and publish it. Unfortunately the build failed almost immediately. 

The build specifically failed on the Restore NuGet packages with the following error message:

The nuget command failed with exit code(1) and error(System.InvalidCastException: Unable to cast object of type 'System.String' to type 'NuGet.Frameworks.NuGetFramework'.

Here are the related build logs:

2019-03-15T15:58:27.7657780Z Attempting to pack file: D:\b\4\agent\_work\83\s\SOFACore\SOFACore.Logging.Exceptions\SOFACore.Logging.Exceptions.csproj

2019-03-15T15:58:27.7706605Z [command]D:\b\4\agent\_work\_tool\NuGet\4.1.0\x64\nuget.exe pack D:\b\4\agent\_work\83\s\SOFACore\SOFACore.Logging.Exceptions\SOFACore.Logging.Exceptions.csproj -NonInteractive -OutputDirectory D:\b\4\agent\_work\83\a -Properties Configuration=Release -version 1.0.0-CI-20190315-165827 -Verbosity Detailed

2019-03-15T15:58:29.7910390Z System.InvalidCastException: Unable to cast object of type 'System.String' to type 'NuGet.Frameworks.NuGetFramework'.

2019-03-15T15:58:29.7910390Z    at NuGet.ProjectManagement.NuGetProject.GetMetadata[T](String key)

2019-03-15T15:58:29.7920155Z NuGet Version: 4.1.0.2450

2019-03-15T15:58:29.7920155Z    at NuGet.ProjectManagement.PackagesConfigNuGetProject..ctor(String folderPath, Dictionary`2 metadata)

2019-03-15T15:58:29.7920155Z Attempting to build package from ‘SOFACore.Logging.Exceptions.csproj'.

2019-03-15T15:58:29.7920155Z    at CallSite.Target(Closure , CallSite , Type , Object , Dictionary`2 )

2019-03-15T15:58:29.7920155Z MSBuild auto-detection: using msbuild version '15.9.21.664' from 'D:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\bin'. Use option -MSBuildVersion to force nuget to use a specific version of MSBuild.

2019-03-15T15:58:29.7920155Z    at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2)

2019-03-15T15:58:29.7920155Z    at NuGet.CommandLine.ProjectFactory.AddDependencies(Dictionary`2 packagesAndDependencies)

2019-03-15T15:58:29.7920155Z    at NuGet.CommandLine.ProjectFactory.ProcessDependencies(PackageBuilder builder)

2019-03-15T15:58:29.7929920Z    at NuGet.CommandLine.ProjectFactory.CreateBuilder(String basePath, NuGetVersion version, String suffix, Boolean buildIfNeeded, PackageBuilder builder)

2019-03-15T15:58:29.7929920Z    at NuGet.Commands.PackCommandRunner.BuildFromProjectFile(String path)

2019-03-15T15:58:29.7929920Z    at NuGet.CommandLine.PackCommand.ExecuteCommand()

2019-03-15T15:58:29.7929920Z    at NuGet.CommandLine.Command.ExecuteCommandAsync()

2019-03-15T15:58:29.7929920Z    at NuGet.CommandLine.Command.Execute()

2019-03-15T15:58:29.7929920Z    at NuGet.CommandLine.Program.MainCore(String workingDirectory, String[] args)

2019-03-15T15:58:29.7929920Z Packing files from 'D:\b\4\agent\_work\83\s\SOFACore\VLM.SOFACore.Logging.Exceptions\bin\Release\netstandard2.0'.

2019-03-15T15:58:29.7929920Z Add file 'D:\b\4\agent\_work\83\s\SOFACore\VLM.SOFACore.Logging.Exceptions\bin\Release\netstandard2.0\VLM.SOFACore.Logging.Exceptions.dll' to package as 'lib\netstandard2.0\VLM.SOFACore.Logging.Exceptions.dll'

2019-03-15T15:58:29.8379110Z ##[error]The nuget command failed with exit code(1) and error(System.InvalidCastException: Unable to cast object of type 'System.String' to type 'NuGet.Frameworks.NuGetFramework'.

   at NuGet.ProjectManagement.NuGetProject.GetMetadata[T](String key)

   at NuGet.ProjectManagement.PackagesConfigNuGetProject..ctor(String folderPath, Dictionary`2 metadata)

   at CallSite.Target(Closure , CallSite , Type , Object , Dictionary`2 )

   at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2)

   at NuGet.CommandLine.ProjectFactory.AddDependencies(Dictionary`2 packagesAndDependencies)

   at NuGet.CommandLine.ProjectFactory.ProcessDependencies(PackageBuilder builder)

   at NuGet.CommandLine.ProjectFactory.CreateBuilder(String basePath, NuGetVersion version, String suffix, Boolean buildIfNeeded, PackageBuilder builder)

   at NuGet.Commands.PackCommandRunner.BuildFromProjectFile(String path)

   at NuGet.CommandLine.PackCommand.ExecuteCommand()

   at NuGet.CommandLine.Command.ExecuteCommandAsync()

   at NuGet.CommandLine.Command.Execute()

   at NuGet.CommandLine.Program.MainCore(String workingDirectory, String[] args))

2019-03-15T15:58:29.8388875Z ##[error]An error ocurred while trying to pack the files.

2019-03-15T15:58:29.8388875Z ##[section]Async Command Start: Telemetry

2019-03-15T15:58:29.8388875Z ##[section]Async Command End: Telemetry

2019-03-15T15:58:29.8398640Z ##[section]Async Command Start: Telemetry

2019-03-15T15:58:29.8398640Z ##[section]Async Command End: Telemetry

2019-03-15T15:58:29.8398640Z ##[section]Finishing: NuGet pack

So what is the problem?

This seems to be a known problem;https://github.com/NuGet/Home/issues/4808. The NuGet 4.0 pack command cannot handle .NET Core(and .NET Standard) projects.

There are 2 possible solutions:

  1. Switch to the .NET Core build task and invoke the dotnet restore command.
  2. Use the NuGet Tools installer build task to install a newer version of Nuget exe (NuGet 4.9.4 seems to work)
Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more