attempt to fix pathToExtension in FsiExtension tests.

[smoothdeveloper]

No description provided.

[smoothdeveloper]

I'm actually confused with <OutputPath> not being honored on a call to build.cmd.

[forki]

yeah I'm confused as hell

[smoothdeveloper]

Ok, there is a problem with the output path being inconsistent between build from IDE and build script, the other issue I suspect is that we need a binding redirect for another assembly than just FSharp.Core in the FCS test.

For the first issue, something like the pathToExtension hack in this branch may be good work around for now.

For the second, this is confusing error because the loading mechanism will silently move on from an extension assembly that can't be loaded (due to binding redirect issue), this is the reason

Paket/integrationtests/Paket.IntegrationTests/FsiExtension.fs

Lines 21 to 29 in fc90013

	System.AppDomain.CurrentDomain.add_AssemblyResolve(fun _ (e: System.ResolveEventArgs) ->
	// the paket dependency manager assembly depends on fsharp.core version
	// which may not be the same as hosting process
	if e.Name.StartsWith "FSharp.Core," then
	printfn "binding redirect for FSharp.Core..."
	typedefof<Map<_,_>>.Assembly
	else
	e.RequestingAssembly
	)

was put in place.

Does FSharp.Core 5 depends on additional thing?