LINQPAD is supplying runtime versioning policy to make this work

WAMRA

LINQPAD is supplying runtime versioning policy to make this work

If I am using a package from NuGet and it has a dependency on another shared library; -nlog for example xx.xx.xx.1-

I want to be able to force a redirection to use my local different version of that library xx.xx.xx.2

I am sure it will work. Is there a way to do that in linqpad ?

I am trying to combine my local libraries which use TIBCO with the version that RxHeat is referencing.

JoeAlbahari

With NuGet references, LINQPad manages the dependency versioning by following the rules in the NuGet package manifest. There's no way to change this other than updating the package manifest.

WAMRA

ok, any idea if there is a way to get the intellisense to work in this case. LinqPad's intellisense doesn't seems to work when it supplies a run time versioning~redirection.