Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator >= 1.0.2 + e.g. Microsoft.Win32.Registry = warning
See original GitHub issueInvestigative information
As in title, having Microsoft.Win32.Registry and Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator in version higher than 1.0.1 in the same project causes warning.
Repro steps
Create console app project with such csproj and try to build it.
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>netcoreapp2.2</TargetFramework>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Microsoft.Win32.Registry" Version="4.7.0" />
<PackageReference Include="Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator" Version="1.0.2" />
</ItemGroup>
</Project>
Expected behavior
No warning.
Actual behavior
Following warning:
Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.targets(33, 5): Could not evaluate 'Microsoft.Win32.Registry.dll' for extension metadata. Exception message: Could not load file or assembly 'Microsoft.Win32.Registry, Version=4.1.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
Known workarounds
Downgrading a package to at least 1.0.1
Related information
One might argue that this behavior is appropriate. Maybe. I’m not familiar with these packages’ content.
But having
- Microsoft.NET.Sdk.Functions > 1.0.24 depending on Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator > 1.0.1
- System.Data.SqlClient = 4.8.0 depending on Microsoft.Win32.Registry
causes my pipelines to fail because I treat warnings as errors and I cannot really accept this. Issue on the Azure Function SDK side is hanging as opened since March 2019.
Thank you for your reply.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thank you for your time. It seems that project migration to .NET Core 3.1 is my best bet then. Nevertheless, I consider removal of this warning as an worthwhile improvement that I hope will happen soon.
Yeah, we’re working on that too but our function apps are stuck on 2.2 from another issue with the azure functions library.