Hello,
I'm sorry it's taken awhile to get back to you. I've done some research on this and it appears this can happen because of assembly trusts. If the assembly you're profiling is fully trusted, the .net Framework doesn't do byte code verification.
I'm assuming that since the assembly is being started by Profiler, it would get a different security trust level and .net would verify the code, finding the error when launching the program on its' own would not.
Can you please try adding the RedGate.ANTS.Profiler.UI.exe to your fully-trusted assemblies and see if that helps?
I'm sorry it's taken awhile to get back to you. I've done some research on this and it appears this can happen because of assembly trusts. If the assembly you're profiling is fully trusted, the .net Framework doesn't do byte code verification.
I'm assuming that since the assembly is being started by Profiler, it would get a different security trust level and .net would verify the code, finding the error when launching the program on its' own would not.
Can you please try adding the RedGate.ANTS.Profiler.UI.exe to your fully-trusted assemblies and see if that helps?