ICSharpCode.NRefactory.Cecil

Allows loading an IProjectContent from an already compiled assembly.

Instance methods are not thread-safe; you need to create multiple instances of CecilLoader if you want to load multiple project contents in parallel.

Version number of the cecil loader. Should be incremented when fixing bugs in the cecil loader so that project contents cached on disk (which might be incorrect due to the bug) are re-created.

Initializes a new instance of the class.

Initializes a new instance of the class.

If true references to the cecil objects are hold. In this case the cecil loader can do a type system -> cecil mapping.

Creates a nested CecilLoader for lazy-loading.

Loads the assembly definition into a project content.

Unresolved type system representing the assembly

Loads the module definition into a project content.

Unresolved type system representing the assembly

Sets the current module. This causes ReadTypeReference() to use for references in that module.

Loads a type from Cecil.

The Cecil TypeDefinition. ITypeDefinition representing the Cecil type.

Reads a type reference.

The Cecil type reference that should be converted into a type system type reference. Attributes associated with the Cecil type reference. This is used to support the 'dynamic' type.

Reads a security declaration.

Given an assembly that was created by the CecilLoader with lazy-loading enabled, this method will eagerly load all classes, and free any references to the source Cecil objects. The intended usage pattern for this method is: 1. use lazy-loading to improve the latency when new assemblies have to be loaded 2. later, when the CPU is idle, call FinishLazyLoading() to free up the memory consumed by the Cecil objects

Specifies whether to use lazy loading. The default is false. If this property is set to true, the CecilLoader will not copy all the relevant information out of the Cecil object model, but will maintain references to the Cecil objects. This speeds up the loading process and avoids loading unnecessary information, but it causes the Cecil objects to stay in memory (which can significantly increase memory usage). It also prevents serialization of the Cecil-loaded type system.

Because the type system can be used on multiple threads, but Cecil is not thread-safe for concurrent read access, the CecilLoader will lock on the instance for every delay-loading operation. If you access the Cecil objects directly in your application, you may need to take the same lock.

This delegate gets executed whenever an entity was loaded.

This callback may be to build a dictionary that maps between entities and cecil objects. Warning: if delay-loading is used and the type system is accessed by multiple threads, the callback may be invoked concurrently on multiple threads.

Gets a value indicating whether this instance stores references to the cecil objects.

true if this instance has references to the cecil objects; otherwise, false.