Am Dienstag, 25. März 2014 21:34:40 UTC+1 schrieb Jb Evain: > > This has no meaning? :) >
Well, to you it certainly has a meaning. To me it might mean a lot less or something different. > A documentation would read like: An assembly resolver is responsible > for resolving references to an assembly into its definition. > The documentation could go more into details of the behaviour or expectations which is not obvious from the name alone. Like the purpose of the cache. > (Which is arguably the same has the above, just a different language :) > Which would be a stub, not a real documentation. Robots are generating such stubs. > It's not a completely straightforward process, if you want a complete > understanding you can checkout and build Cecil in your project and > step into the code. > That's what I do all the time. It already helps a lot, but not always. > The default resolver only caches the assemblies it resolves. Not those > you read yourself. Meaning, if you use ModuleDefiniton.ReadModule or > AssemblyDefinition.ReadAssembly, those won't be cached for you. > This is a very good start for a documentation. :-) > You can easily implement that by creating your own class extending > DefaultAssemblyResolver, and calling RegisterAssembly on existing > assemblies. > Thank you, that works fine. I'm just wondering why that method isn't public so I could simply call it on DefaultAssemblyResolver. Now I need to create a class whose only purpose is to make a non-public member public. -- -- -- mono-cecil --- You received this message because you are subscribed to the Google Groups "mono-cecil" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
