THE BORE

General => The Superdeep Borehole => Topic started by: recursivelyenumerable on November 11, 2009, 01:23:55 AM

Title: ITT we blame all our MIA-in-fuslogvw .NET assembly binding failures on Prole
Post by: recursivelyenumerable on November 11, 2009, 01:23:55 AM

 :maf :maf :maf :maf :maf :maf :maf :maf :maf :maf :maf

Title: Re: ITT we blame all our MIA-in-fuslogvw .NET assembly binding failures on Prole
Post by: Van Cruncheon on November 11, 2009, 02:42:53 AM

something something appdomain and the gac

Title: Re: ITT we blame all our MIA-in-fuslogvw .NET assembly binding failures on Prole
Post by: recursivelyenumerable on November 11, 2009, 02:52:50 AM

it was actually in a .NET assembly being called via COM from something else, and was happening because I had a wrong Assembly value in the registry under InprocServer32, which apparently put the error in some limbo where the COM class loading problem doesn't show up in Process Monitor, but the .NET assembly binding problem doesn't show up in the fusion logs either.  very devious, curse you!