cecil icon indicating copy to clipboard operation
cecil copied to clipboard

Cecil is a library to inspect, modify and create .NET programs and libraries.

Results 125 cecil issues
Sort by recently updated
recently updated
newest added

Instruction.ToString() uses the culture of the current thread, which can be problematic for converting doubles and floats to a string.

Instead of going into a long tirade about the lack of documentation for a long running project, and how it make uptake much harder for quick one-off projects, \- as...

This is required by the Portable PDB specification, and the sequence point collection in `MethodDebugInfo` does not guarantee it. This also tweaks the writing of hidden sequence points to use...

Basically the first two entries are written correctly, and any after that which has data will have the RVA correct, but the virtual address field will be wrong. Depending on...

Calling `ModuleDefinition.Write` multiple times generates different outputs. The first output is binary different from all subsequent outputs. This is not a blocking issue, since both outputs seem to work fine,...

When editing IL with ILProcessor various pieces of debug information have references to the origin IL instructions. These references can be either resolved (point to Instruction instance), in which case...

This is a change towards addressing the platform dependent behaviour of the Cecil binaries when resolving system assemblies. This change extracts the net core and framework system assembly search strategies...

An assembly built to target the .Net Framework expects to resolve system references in the GAC; however a .net (core) program using Cecil to manipulate that assembly resolves them to...

With the latest changes 79b43e8 in `PortablePdb.cs` assemblies modified with cecil can no longer be debugged in VisualStudio when embedded pdbs are used. See https://github.com/Fody/Fody/issues/1110 for details how to reproduce.

If the user reads an assembly, which has a portable PDB, using AssemblyDefinition.ReadAssembly(fileName, readerParams) then it is seen that after this call is completed, the PDB file handle is kept...