Tuesday, November 02, 2010 8:08 PM
After upgrading CCR from 2.0.913.0 to 184.108.40.206 we started randomly getting System.NullReferenceException in Microsoft.Ccr.Core.CausalityThreadContext.RequiresDebugBreak()
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Ccr.Core.CausalityThreadContext.RequiresDebugBreak(CausalityThreadContext context)
at Microsoft.Ccr.Core.TaskExecutionWorker.ExecuteTaskHelper(ITask currentTask)
at Microsoft.Ccr.Core.TaskExecutionWorker.ExecuteTask(ITask& currentTask, DispatcherQueue p, Boolean bypassExecute)
Quick look into the code using Reflector showed that that RequiresDebugBreak() didn't even exist in the old version so it must be something new introduced in the latest one.
Do you think we do something wrong and this is why we get the exception or it's a bug in the new version.
If it's a bug can we get it fixed?
Thursday, November 04, 2010 4:36 PMI remember readin in he forum RequiresDebugBreak should not have been public method. You should have not use this method. Ido
Thursday, November 04, 2010 7:22 PMI don't use that method directly. CCR throws that exception internally
Tuesday, October 04, 2011 6:45 PMModeratorThis is fixed in RDS4