Dogfooding?
-
I'm currently trying to write LinFu v2.0, but the problem is that one of the components it needs to verify the IL that v2 generates requires a dynamic proxy generator of its own. The problem is that if I have it depend on version 1.0, I'll end up with either a circular dependency on the old framework, and if I rely on someone else's dynamic proxy (and break the circular dependency), it'll be a bit embarrassing on my part. Is there any way around this, or should I just bite the bullet and try someone else's dynamic proxy generator for the sake of the IL verifier?
Do you know...LinFu?
-
I'm currently trying to write LinFu v2.0, but the problem is that one of the components it needs to verify the IL that v2 generates requires a dynamic proxy generator of its own. The problem is that if I have it depend on version 1.0, I'll end up with either a circular dependency on the old framework, and if I rely on someone else's dynamic proxy (and break the circular dependency), it'll be a bit embarrassing on my part. Is there any way around this, or should I just bite the bullet and try someone else's dynamic proxy generator for the sake of the IL verifier?
Do you know...LinFu?
To avoid the circular dependency, you could always dynamically invoke the dynamic proxy generator.
Deja View - the feeling that you've seen this post before.
-
To avoid the circular dependency, you could always dynamically invoke the dynamic proxy generator.
Deja View - the feeling that you've seen this post before.
Pete O'Hanlon wrote:
To avoid the circular dependency, you could always dynamically invoke the dynamic proxy generator.
I could do that, but in this case I've changed my mind and decided not to use a dynamic proxy generator at all. I'll just have to bite the bullet and do my IL verification with either PEVerify, or in the worst case, I'll write my own runtime verifier. Thanks anyway, Pete! :)
Do you know...LinFu?