Stuck on an issue?

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.

Visual Studio 2017 RC cannot find Microsoft.Build.Framework

See original GitHub issue

Cross posting from the Costura repo where I originally posted this https://github.com/Fody/Costura/issues/173

Seems that an unmodified project that is building fine in VS2015 using Costura.Fody can’t find the Microsoft Build framework and throws the following exception at compile time

Error       Fody: An unhandled exception occurred:
Exception:
Could not load file or assembly 'Microsoft.Build.Framework, Version=15.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
StackTrace:

Server stack trace: 
   at System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
   at System.Reflection.RuntimeMethodInfo.FetchNonReturnParameters()
   at System.Reflection.RuntimeMethodInfo.GetParameters()
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at IInnerWeaver.set_Logger(ILogger value)
   at Processor.ExecuteInOwnAppDomain() in c:\ConsoleBuildAgent\work\ed448661dbb30d2e\Fody\Processor.cs:line 146
   at Processor.Inner() in c:\ConsoleBuildAgent\work\ed448661dbb30d2e\Fody\Processor.cs:line 93
   at Processor.Execute() in c:\ConsoleBuildAgent\work\ed448661dbb30d2e\Fody\Processor.cs:line 45
Source:
mscorlib
TargetSite:
Void GetSignature(Void*, Int32, System.RuntimeFieldHandleInternal, System.IRuntimeMethodInfo, System.RuntimeType)
Could not load file or assembly 'Microsoft.Build.Framework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
StackTrace: DiagnosticsSharp.Runner

Issue Analytics

State:
Created 7 years ago
Comments:27 (14 by maintainers)

Top GitHub Comments

10reactions

rvheldencommented, Feb 9, 2017

Sorry I have found the problem, my project was using an older version of Fody, I have upgraded the package to version 29 and everything is working now

5reactions

atzimlercommented, Mar 14, 2017

I’ve just run into this problem today. It seems to go away if you install MSBuild version 14 - which is the one associated with VS2015. https://www.microsoft.com/en-us/download/details.aspx?id=48159

Top Results From Across the Web

Could not load file or assembly 'Microsoft.Build.Framework' ...

The system cannot find the file specified.' I am using Visual Studio 2017 and was trying to do Update-Database after Add-Migration .

MSBuild 14.0 cannot find RC after installing VS2017 ...

https://developercommunity.visualstudio.com/content/problem/65345/msbuild-140-cannot-find-rc-after-installing-vs2017.html.

Find and use a version of MSBuild

In this article · Use Microsoft.Build.Locator · Change MSBuild references · Ensure output is clean · Add package reference for Microsoft.Build.

MSBuild forum - RSSing.com

MSBuild requires Visual studio 2017/19 to be installed on the PC where it runs, in order to be able to compile C and...

Msbuild not found. This is due to your VCTargetsPath path ...

In my case I copied the Reporting Services folder from C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild on my developer PC to …