The package on nuget is quite stable. There hasn't been much important changes between the last push on nuget and master.
That being said, Cecil does have a pretty extensive test suite, so it's always possible that you hit bugs in Cecil, but it's a lot more likely that you're introducing errors when injecting custom IL. Jb On Fri, Mar 21, 2014 at 10:22 PM, Yves Goergen <[email protected]> wrote: > Currently I'm using the source files of Mono Cecil 0.9. Reading the commit > history, I found that the last release of the Nuget package has some version > 0.9.5, IIRC. This is already a lot younger than 0.9. After that there comes > still a number of commits that contain "fix" or the like in their message. > > I'm wondering what version/revision of Cecil I should use to get the most > stable result, with the least number of bugs anywhere. Is this always the > most recent commit? Or only most of the time? Or should I stay a few weeks > behind? Or is something labelled "release" (for Nuget for example) the > safest bet? > > Right now I'm hunting some PEVerify errors in my processed assembly and I'd > like to do everything possible that I don't hit any Cecil bug here. But I'm > also reading more into CIL right now, to understand the raw data that ILDASM > presents to me. (Which I believe is perfectly fine, yet there is something > that PEVerify doesn't like in it...) > > -- > -- > -- > 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. -- -- -- 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.
