Manifest definition12/28/2022 ![]() ![]() I packed the nuget packages for all projects using Yaml with a task: - task: 'pack' I had by accident added version-tag in the *.csproj files like this: I had a solution with many projects for my own nuget packages. The problem was somewhat different than the other answers try to solve, so I will share my solution. This question is quite old, and I had the same error message recently with Azure DevOps Yaml pipelines and Dotnet Core 3.1. Also note that the public key and culture are important and dotPeek also show this information. dotPeek says it is 4.2.1.0 and that is the version that works correctly in our software. MANIFEST DEFINITION WINDOWSWindows explorer says the file is 5.06, nuget says its a 5.0.0.0 file. So for example, the correct binding for this file is the following: The assembly name listed in dotPeek is always accurate in my experience. The only way to get correct version info is to analyse the file itself. Windows properties is not always accurate and nuget is also not always accurate. However, that's only part of the problem - you need to know the correct version of the assembly file that you're using. If not, add any missing binding redirects that the package console missed.Ī general answer to this kind of issue is to use binding redirects as in other answers.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |