I just thought of something. Would it be possible to just mark my injected IL as hidden (16707566 is 0xfeefee in hexa)?
Would that maybe remove the need to update the sequence points in the first place? Regards Bernhard Richter On Apr 24, 10:28 am, seesharper <[email protected]> wrote: > Hi again and thanks for your quick response. > > And yes, basically what I'm looking for is a way to load the symbols > using a byte array. > > And just to be sure that I make myself clear. > > I have this files on disc > > TestLibrary.dll > > TestLibrary.pdb > > TestLibrary.dll is loaded dynamically and modified before loaded into > the main appdomain. > > I guess at that point the sequence points are out of sync? > > Regards > > Bernhard Richter > > On Apr 24, 10:16 am, Jb Evain <[email protected]> wrote: > > > Hey, > > > On 4/24/09, seesharper <[email protected]> wrote: > > > > 1. The SaveSymbols seems to update the pdb on disc while I want > > > "updated" debug information that can be loaded into the main appdomain > > > using the > > > public static Assembly Load(byte[] rawAssembly,byte[] rawSymbolStore) > > > overload. > > > Right, we don't support a way to get a byte[] containing the pdb, > > unless you store both the assembly and the pdb on disc. I'll have a > > look at what Cecil and Cecil.Pdb can do. > > > > 2. Even when trying to modify the pdb (using SaveSymbols()) on disc it > > > seems to fail and somehow mess up the debug info even if I did not > > > make any changes to the assembly in the first place. > > > You probably have a mismatch between the pdb and the assembly. We > > still have a known issue with the pdbwriter, which sometimes emits a > > wrong debug header in the assembly, but otherwise, that part is > > working. > > > -- > > Jb Evain <[email protected]> > > --~--~---------~--~----~------------~-------~--~----~ -- mono-cecil -~----------~----~----~----~------~----~------~--~---
