Thank you JB. It helped. PEVerify is showing the errors and trying to fix them.
Thanks, Venu On Monday, October 1, 2018 at 9:26:02 PM UTC+5:30, Jb Evain wrote: > Hello, > > It sounds like there's a bug in your instrumentation that ends up > triggering a pretty bade exception :) > > The best way to tackle issues like that is to run the tool `peverify` from > the .NET Framework SDK on your instrumented assemblies. > > Jb > > On Mon, Oct 1, 2018 at 3:26 AM venu gopal Yela <[email protected] > <javascript:>> wrote: > >> Hi JB, >> >> We are successfully using Mono Cecil to instrument .Net assemblies and >> running the instrumented assemblies in Visual Studio. >> Recently for one of the assemblies, we are getting error >> "System.ExecutionEngineException" at runtime. >> And Visual Studio is not showing class name/method name that caused this >> error. >> >> .Net Version is 3.5 and Visual Studio is 2009. >> >> Tried all the possible options that we can. >> Is this related to Windows and .Net Version & Visual Studio Version? >> >> Can you please help? >> >> Thanks, >> Venu >> >> -- >> -- >> -- >> 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] <javascript:>. >> 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.
