Closed davidkeaveny closed 5 years ago
@davidkeaveny you aren't missing anything I started signing Grace a while back and it makes it incompatible with some of the older side libraries like Grace.Net. That said now that .netstandard 2.0 support Assembly.Load I can upgrade Grace.Net to both standard and .net 4.5.
For the moment you can probably just copy the methods from here and I can put together something in the coming days.
@davidkeaveny So I took a look at the Grace.Net
library last night and everything other than the Types
static class is related to System.Configuration
.
I think what I'm going to do is create a documentation section for this and put the class their and you can just add it directly to your project. The reality is they are just simple wrappers around Assembly.Load
and don't require their own libraries.
Does that seem like a reasonable solution?
Never heard back so I'm marking as closed
Maybe I'm just tired and had enough of banging my head against .NET's assembly loading code, but I cannot get the following code to run:
Instead, it throws a TypeInitializationException, which is complaining about loading Grace 4.0.2 (which is the version that Grace.Net links to, although I am running Grace 6.4.0). I've tried adding an assembly binding redirect for Grace to 6.4.0 but to no avail.
My Fusion log appears below:
Cracking open the assemblies in dotPeek, Grace 6.4.0 has a public key token (b7d24c6367970497) while the reference held by Grace.Net has a public key token of null. Is there something I'm missing?
P.S. This is built and run under .NET Framework 4.7.2 on Windows 10 Professional.