Add MSBuild assembly binding redirect about fsautocomplete HOT 8 CLOSED

I'm not sure if this would help, actually.

• If we add binding redirect to version of MSBuild that is included with VS 2015, we break VS 2013
• If we add binding redirect to version of MSBuild that is included with VS 2013, we break VS 2015

Or am I missing some magical trick? Like binding redirect to "whatever can be found"?

from fsautocomplete.

Hmm, maybe you're right actually. This whole thing is a bit of a can of worms.

from fsautocomplete.

I found the magical trick: https://github.com/rneatherway/msbuildresolution/blob/master/MSBuildResolution/Program.fs#L377

I am using a standard redirect to get up to MSBuild v12 (VS2013), with a special event handler to try MSBuild v14 (VS2015) as a backup.

from fsautocomplete.

Maybe this can be refined so that an array of assemblies and binding
versions can be passed in, the first one found is then bound.

On 9 August 2015 at 14:33, Robin Neatherway [email protected]
wrote:

I found the magical trick:
https://github.com/rneatherway/msbuildresolution/blob/master/MSBuildResolution/Program.fs#L377

I am using a standard redirect to get up to MSBuild v12 (VS2013), with a
special event handler to try MSBuild v14 (VS2015) as a backup.

—
Reply to this email directly or view it on GitHub
#11 (comment)
.

from fsautocomplete.

Yes sure, what do you imagine using that for?

It's worth noting that this handler only executes if the assembly resolution fails, so we still need the standard App.config binding redirect as well to pull MSBuild v4 up to at least v12.

from fsautocomplete.

To avoid three calls in the event handler

On 10 August 2015 at 11:05, Robin Neatherway [email protected]
wrote:

Yes sure, what do you imagine using that for?

It's worth noting that this handler only executes if the assembly
resolution fails, so we still need the standard App.config binding
redirect as well to pull MSBuild v4 up to at least v12.

—
Reply to this email directly or view it on GitHub
#11 (comment)
.

from fsautocomplete.

Ah I see. The one I'm adding to FsAutoComplete will just redirect all Microsoft.Build* assemblies, so that should be OK. If I get that working, then we can look at combining your external process stuff with this into FCS.

from fsautocomplete.

Fixed by #57

from fsautocomplete.