AsmSpy | Simple command line assembly reference checker
kandi X-RAY | AsmSpy Summary
kandi X-RAY | AsmSpy Summary
A simple command line tool to view assembly references.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of AsmSpy
AsmSpy Key Features
AsmSpy Examples and Code Snippets
Community Discussions
Trending Discussions on AsmSpy
QUESTION
The build log from Visual Studio 2017 (15.5.4) has left me stumped on how to get rid of the warning
...Found conflicts between different versions of "Microsoft.WindowsAzure.Storage" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed. Animals.Swine.Functions C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets
ANSWER
Answered 2018-Feb-08 at 09:49How can I figure out where the Storage 8.1.1.0 reference is coming from?
Build log can help us resolve most of the issues, but it does not resolve all the issues. It still need us to troubleshootings those issues manually. Because Visual Studio/MSBuild could not be smart to directly find the root cause of the issue.
When we meet this MSB3247/MSB3277 error, the best way to resolve this issue is turn MSBuild output log to Diagnostic (Tools->Options->Project and Solutions->Build and Run, set MSBuild project build output verbosity), then find the references which depend on Microsoft.WindowsAzure.Storage
, check if there are different versions of Microsoft.WindowsAzure.Storage
being referenced.
In the build log, we found that Project file item includes which caused reference Microsoft.Azure.WebJobs.2.1.0
and Microsoft.Azure.WebJobs.Extensions.2.0.0
Then check the dependencies of those two packages, none of them have reference to Microsoft.WindowsAzure.Storage, Version=8.1.1.0
.
In order to confirm it, you can use the method which provided by Vladimir in the comment.
At this moment, this conflict should not come from references. Then we should check the file related to reference version, for example, app.confi
g or web.config
, find binding redirect about reference Microsoft.WindowsAzure.Storage
, check if binding redirect is correct.
So sometimes we can not directly solve the problem based only on build log information, manual troubleshooting is also essential.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install AsmSpy
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page