Just getting back to this now...
Both assemblies are referencing the .NET 3.5 version of Autofac and the 4.0
version is out because these assemblies are being loaded into a .NET 3.5
process (3rd party native app that hosts .NET 3.5 for plugins).
To add a probing path it would need to go in the
Can't help, but that sounds like a well enough explained problem for
stackoverflow.com.
--
Regards,
Mark Hurd, B.Sc.(Ma.)(Hons.)
On 19 September 2011 15:57, Matt Siebert mlsieb...@gmail.com wrote:
Hi all,
I have some assembly binding weirdness happening that I don't fully
understand. I have
Matt, can you try and use a probe path using a symbolic linked subdirectory
to the real directory?
On 19 September 2011 18:27, Matt Siebert mlsieb...@gmail.com wrote:
Hi all,
I have some assembly binding weirdness happening that I don't fully
understand. I have some theories but I'd like to
If overrides are not getting called, then is a sign that the runtime seeing
that that the virtual method takes a different ContainerBuilder type (ie 3.5)
to the override (4.0 or vice versa) and hence are not seen as compatible.
I just ran this by Nick (who owns Autofac and is down the hall from
