Getting NU1202 error when running Nuget restore

Question

I have a .NET Framework solution that I'm trying to set up with a pipeline on Azure DevOps. I'm getting an error when trying to restore packages though:

NU1202: Package AppCenter.Analytics.Metrics 1.1.0 is not compatible with net40 (.NETFramework,Version=v4.0). Package AppCenter.Analytics.Metrics 1.1.0 supports: netstandard1.0 (.NETStandard,Version=v1.0)

And many more like this. It's right - that package isn't compatible with net40, but it shouldn't matter. There are several projects in the solution, but the oldest .NET version is 4.5, so I can't figure out where the v4.0 is coming from in the above. Other things that may be relevant:

The build output reports a NuGet version of 5.3.1.6268 and MSBuild version of 16.3.2.50909.
The solution restores and builds correctly locally.
I noticed a "v4.0" in the .sln.metaproj file: v4.0. That seems relevant, but I can't figure out where it's coming from or how to change it. Azure devops doesn't see this file as it's ignored by git, but I wonder what's causing that 4.0 there.

Here's a snippet from the pipeline.yaml:

pool:
  vmImage: 'windows-latest'

variables:
  solution: '**/*.sln'
  buildPlatform: 'Any CPU'
  buildConfiguration: 'Release 2019'

steps:
- task: NuGetToolInstaller@1

- task: NuGetCommand@2
  inputs:
    command: 'restore'
    restoreSolution: '$(solution)'
    feedsToUse: 'select'
    vstsFeed: '#####'

And here's one of the offending csproj files. There's some funny business for targeting multiple versions of Revit, and finding the location of Rhino dlls, but I can't see anything that would lead to trying to install packages for .NET v4.0:



  
    $([MSBuild]::GetRegistryValueFromView('HKEY_LOCAL_MACHINE\SOFTWARE\McNeel\Rhinoceros\7.0\Install', 'Path', null, RegistryView.Registry64))
    $([MSBuild]::GetRegistryValueFromView('HKEY_CURRENT_USER\Software\McNeel\Rhinoceros\7.0-WIP-Developer-Debug-trunk\Install', 'Path', null, RegistryView.Registry64))
    $([MSBuild]::ValueOrDefault('$(Rhino7DebugInstallDir)', '$(Rhino7DefaultInstallDir)'))
    $([MSBuild]::GetRegistryValueFromView('HKEY_LOCAL_MACHINE\SOFTWARE\McNeel\Rhinoceros\7.0\Install', 'Default Plug-ins Folder', null, RegistryView.Registry64))
    $([MSBuild]::GetRegistryValueFromView('HKEY_CURRENT_USER\Software\McNeel\Rhinoceros\7.0-WIP-Developer-Debug-trunk\Install', 'Default Plug-ins Folder', null, RegistryView.Registry64))
    $([MSBuild]::ValueOrDefault('$(Rhino7DebugPluginsDir)', '$(Rhino7DefaultPluginsDir)'))
  
  
  
    v4.6.2
    2018
  
  
    v4.7.2
    2019
  
  
    v4.7.2
    2020
  
  
    
    $(SolutionDir)solution.ruleset
  
  
    
  
  
    Debug
    AnyCPU
    9.0.30729
    2.0
    {D6C256D4-B518-464F-9E68-CB282202E846}
    Library
    Properties
    Namespace
    AssemblyName
    
    
    
  
  
    true
    bin\Debug 2018\
    TRACE;DEBUG;REVIT_2018
    full
    AnyCPU
    prompt
    7.3
  
  
    true
    bin\Release 2018\
    AnyCPU
    REVIT_2018
    true
    7.3
  
  
    true
    bin\Debug 2019\
    TRACE;DEBUG;REVIT_2018; REVIT_2019
    portable
    AnyCPU
    prompt
    7.3
  
  
    true
    bin\Release 2019\
    AnyCPU
    REVIT_2018; REVIT_2019
    true
    7.3
    portable
  
  
    true
    bin\Debug 2020\
    TRACE;DEBUG;REVIT_2018; REVIT_2019; REVIT_2020
    full
    AnyCPU
    prompt
    7.3
  
  
    true
    bin\Release 2020\
    AnyCPU
    REVIT_2018; REVIT_2019; REVIT_2020
    true
    7.3
  
  
    
    
    
    
    
    
    
      False
      C:\Program Files (x86)\Reference Assemblies\Microsoft\WindowsPowerShell\3.0\System.Management.Automation.dll
    
    
    
    
  
  
    ... Files ...
  
  
    
      Designer
      ResXFileCodeGenerator
      Resources.Designer.cs
    
  
 ... More Files in ItemGroups ...
  
    ... Project References ...
  
  
    
      1.1.0
    
    
      2.6.2
    
    
      2.6.2
    
    
      2.9.8
      runtime; build; native; contentfiles; analyzers; buildtransitive
      all
    
    
      1.1.118
      runtime; build; native; contentfiles; analyzers; buildtransitive
      all
    
  
  
    
      
        
          $(Rhino7InstallDir)Eto.dll
          False
        
        
          $(Rhino7InstallDir)RhinoCommon.dll
          False
        
        
          $(Rhino7InstallDir)Rhino.UI.dll
          False
        
        
          $(Rhino7PluginsDir)Grasshopper\GH_IO.dll
          False
        
        
          $(Rhino7PluginsDir)Grasshopper\Grasshopper.dll
          False
        
        
          C:\Program Files\Autodesk\Revit $(RevitVersion)\RevitAPI.dll
          False
        
        
          C:\Program Files\Autodesk\Revit $(RevitVersion)\RevitAPIUI.dll
          False
        
        
          C:\Program Files\Autodesk\Revit $(RevitVersion)\AdWindows.dll
          False
        
      
    
    
      
        
        
        
      
    
  
  
  
    None

I haven't been able to figure out what to check for or how to debug this. Thanks!

LoLance · Accepted Answer

I noticed a "v4.0" in the .sln.metaproj file. I haven't been able to figure out what to check for or how to debug this.

Some tips that may help for trouble-shooting and resolving the issue:

#1. I think the .sln.metaproj in solution folder and .csproj.metaproj in project folder should be excluded from Source Control. At least these files is not recommended to publish to Azure Devops Repos.

Check their content we can find something like



The error message will tell us which project causes the issue. Open the xx.csproj file in Devops Repos to check its content. I assume the version of the project targets v4.0 or one of its targetFrameworks(multi-targeting) is v4.0. And if that project is a sdk-format project, you may need to use dotnet restore task to restore packages for that.

Update:

See here, nuget restore command won't receive and recognize build configuration. So for this situation, nuget can't access the propertyGroup whose conditions is $(Configuration.Contains('xxx')). Then it is equivalent to nuget restore xx.sln=>nuget restore one project whose TargetFrameworkVersion is empty.And then nuget will consider this project uses default 4.0. So the issue occurs.

Steps to reproduce:

1.Create a simple .net framework 4.7 project, add this into xx.csproj:

    
      1.1.0
    


2.Comment the 

3.Save all and nuget restore xx.sln, same issue occurs:



Possible Workaround:

nuget restore won't accept something like nuget restore xx.sln -property:Configuration=xxx like nuget pack command. So this issue will always occur unless we define the valid TargetFramework version in propertyGroup no matter which conditions. (I guess this is not what you want, but this issue cannot be avoided for this situation)

So I think a better choice is to use msbuild /t:restore instead of nuget restore. For VS2017 and above, msbuild has contained the restore option itself. And it works for those .net fx based projects that use PackageReference format.

So you can use VS build task with arguments /t:restore to restore the packages instead of using Nuget restore(this is not suitable for your custom csproj script).

Getting NU1202 error when running Nuget restore

Answers (1)

Related Questions