JB ndepend like most things runs then immediately dies. Memory usage or things like fragmenting the LOH are of little concern. For a longer running app it becomes a big concern. My worry is I will see the same behavior that we currently see. Longer term the answer is probably to build pretty much a duplicate object model on top of cecil but we can't do that now for everything. I was thinking that maybe by using just a simple table by reading symbols directly we could bypass this issue.
Are there any examples available of using the APIs directly? On Fri, Feb 25, 2011 at 10:06 AM, Jb Evain <[email protected]> wrote: > Hi, > > On Fri, Feb 25, 2011 at 3:59 PM, Greg Young <[email protected]> wrote: >> I am a bit worried about memory usage/speed having cecil load symbols >> for everything. I only need it for fields/methods. > > Well, it doesn't load symbols for everything, it only loads what's in > a pdb or a mdb: a IL->Sequence Point mapping per method and variables > names. > >> Are my worries unfounded? > > I don't know. It's worth measuring. NDepend has no issue for instance. > >> Is there any sample code anywhere on how to load the symbols manually >> to get just information such as this. > > There's no API to simply extract the symbols manually in Cecil. You > always use the code that Mono.Cecil.Pdb (Microsoft.Cci.Pdb) and > Mono.Cecil.Mdb (Mono.CompilerServices.SymbolWriter) directly if you > feel like it. > > Jb > > -- > -- > mono-cecil -- Les erreurs de grammaire et de syntaxe ont été incluses pour m'assurer de votre attention -- -- mono-cecil
