You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
System.FormatException: 1 is not a valid value for DateTime ---> System.FormatException: String was not recognized as a valid DateTime.
Result StackTrace:
at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
at System.ComponentModel.DateTimeConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
--- End of inner exception stack trace ---
at System.ComponentModel.DateTimeConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Utility.TypeExtensions.NotDefault(Type type)
at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Utility.EventSourceAnalyzer.TryInvokeMethod(EventSchema eventSchema, EventSource source, ProbeEventListener listener, MethodInfo& method)
at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Utility.EventSourceAnalyzer.ProbeEvent(EventSchema eventSchema, EventSource source)
at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Utility.EventSourceAnalyzer.Inspect(EventSource eventSource)
at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Utility.EventSourceAnalyzer.InspectAll(EventSource eventSource)
at
When the second datetime is removed the test succeeds. Is this an eventsource limitation or a bug in the analyzer? I'm on the latest analyzer package version - 2.0.1406.1
Example event:
The analyzer throws:
When the second datetime is removed the test succeeds. Is this an eventsource limitation or a bug in the analyzer? I'm on the latest analyzer package version - 2.0.1406.1