OutOfProcTaskHostNode.cs (17)
268ErrorUtilities.VerifyThrow(EffectiveConfiguration != null, "We should never have a null configuration during a BuildEngine callback!");
269return EffectiveConfiguration.ContinueOnError;
280ErrorUtilities.VerifyThrow(EffectiveConfiguration != null, "We should never have a null configuration during a BuildEngine callback!");
281return EffectiveConfiguration.LineNumberOfTask;
292ErrorUtilities.VerifyThrow(EffectiveConfiguration != null, "We should never have a null configuration during a BuildEngine callback!");
293return EffectiveConfiguration.ColumnNumberOfTask;
304ErrorUtilities.VerifyThrow(EffectiveConfiguration != null, "We should never have a null configuration during a BuildEngine callback!");
305return EffectiveConfiguration.ProjectFileOfTask;
685return new Dictionary<string, string>(EffectiveConfiguration.GlobalProperties);
745ErrorUtilities.VerifyThrow(_taskHost.EffectiveConfiguration != null, "We should never have a null configuration during a BuildEngine callback!");
746return _taskHost.EffectiveConfiguration.IsTaskInputLoggingEnabled;
1759ErrorUtilities.VerifyThrow(EffectiveConfiguration != null, "We should never have a null configuration when we're trying to log messages!");
1765EffectiveConfiguration.TaskName,
1776ErrorUtilities.VerifyThrow(EffectiveConfiguration != null, "We should never have a null configuration when we're trying to log warnings!");
1789EffectiveConfiguration.TaskName);
1799ErrorUtilities.VerifyThrow(EffectiveConfiguration != null, "We should never have a null configuration when we're trying to log errors!");
1812EffectiveConfiguration.TaskName);