When we run ANTS Performance Profiler with 'line-level and method-level timings; all methods' our Application crashes in DO with a VerificationException.
When we run with 'Method-level timings; all methods', then the program starts.
Regards Paul Sinnema Diartis AG
Message: Operation could destabilize the runtime.
at Xtensive.Storage.Configuration.DomainConfiguration.Load(String name) in c:\Temp\DataObjects.Net\Xtensive.Storage\Xtensive.Storage\Configuration\DomainConfiguration.cs:line 407 at Diartis.KLIB.Model.ModelContext.get_KLIBDomainConfiguration() in C:\KLIB2\trunk\KLIB\KLIBDatabase\ModelContext.cs:line 114 at Diartis.KLIB.Model.ModelContext.get_DBFullName() in C:\KLIB2\trunk\KLIB\KLIBDatabase\ModelContext.cs:line 100 at Diartis.KLIB.Model.ModelContext.get_KLIBDomain() in C:\KLIB2\trunk\KLIB\KLIBDatabase\ModelContext.cs:line 161 at Diartis.KLIB.Model.ModelContext.OpenSession() in C:\KLIB2\trunk\KLIB\KLIBDatabase\ModelContext.cs:line 172 at Diartis.KLIB.Model.ModelContext.get_Instance() in C:\KLIB2\trunk\KLIB\KLIBDatabase\ModelContext.cs:line 63 at Diartis.KLIB.KLIBViewModel.VMContext.get_Instance() in C:\KLIB2\trunk\KLIB\KLIBViewModel\VMContext.cs:line 39 at Diartis.KLIB.KLIBContext..ctor() in C:\KLIB2\trunk\KLIB\KLIBMasks\Base\KLIBContext.cs:line 219 at Diartis.KLIB.KLIBContext.get_Instance() in C:\KLIB2\trunk\KLIB\KLIBMasks\Base\KLIBContext.cs:line 140 at Diartis.KLIB.App.OnStartup(StartupEventArgs e) in C:\KLIB2\trunk\KLIB\KLIB\App.xaml.cs:line 83
Actually, it's difficult to advise anything here, so I'll just list the options:
I think the best option is to check your assemblies with PEVerify to find out the reason:
But IMO, the worst part here is that .NET error reporting in this case is absolutely bad. It writes nothing helping to find the reason in this case. We've been getting this error for few times while developing our Tuples framework - originally it was relying on IL Emit, so we've been getting such exception while debugging it. But currently Tuples are fully based on generics - we switched to this option mainly to make them serializable. So actually, this error is pretty normal, if you use IL Emit, and I'm absolutely sure people using this API simply hates it. I understand Microsoft considers buggy IL normally can't appear - well, actually it can, even if you use only public APIs. So IMO, they should make the error reporting more descriptive in this case.