I'm trying to upgrade the Geotab.Checkmate.ObjectModel nuget package from ver 11.118.421 to ver 11.132.485. However, when I try to run my application after upgrading, I get the following runtime error when authenticating (AuthenticateAsync()) to Geotab: System.PlatformNotSupportedException: Operation is not supported on this platform. at System.Net.Http.HttpClientHandler.set_CheckCertificateRevocationList(Boolean value) at Geotab.Checkmate.Web.HttpMessageHandlerBuilder.PropertySetter.SetCheckCertificateRevocationList(HttpMessageHandler&amp; httpMessageHandler, Nullable`1&amp; value) at Geotab.Checkmate.Web.HttpMessageHandlerBuilder.Build() at Geotab.Checkmate.Web.WebServerInvoker.CreateSharedHttpClient() at Geotab.Checkmate.Web.WebServerInvoker..cctor() As I understand this error message, a newer version of the .NetFramework is needed than what the application is running, which in my case is 4.6.2. Could you please let me know what is the minimum supported .NetFramework version for the latest version of Geotab.Chackmake.ObjectModel.

Getting PlatformNotSupportedException when authenticating to GeoTab

In GeoTab.Checkmate.ObjectModel ver. 11.118.421, the following valid Sort constructor call throws an ArgumentException:Sort sortOptions = new Sort(SortField.IdSortField,
						   SortDirection.Asc,
						   null,
						   null);This is because of a logic bug in the following Sort constructor code 	public Sort(string sortBy, SortDirection? direction = global::Geotab.Checkmate.ObjectModel.SortDirection.Asc, string? offset = null, Id? lastId = null)
	{
		if (SortField.ImplementedSortFields.Contains&lt;string&gt;(sortBy, StringComparer.InvariantCultureIgnoreCase))
		{
			throw new ArgumentException("Use existing implementation of ISort for this field");
		}
 
		SortBy = sortBy;
		SortDirection = direction;
		Offset = offset;
		LastId = lastId;
	}In the if statement, SortField.ImplementedSortFields is a string array that contains all the valid sortBy field names, which means that the exception should only be thrown when Contains returns false.  So, for this to work correctly, the return value of Contains should have been inverted, meanting the if statement should look lie this: if (!SortField.ImplementedSortFields.Contains&lt;string&gt;(sortBy, StringComparer.InvariantCultureIgnoreCase))
{
	throw new ArgumentException("Use existing implementation of ISort for this field");
}I've been able to work around this by passing an invalid sortBy value and then changing the SortBy property value Sort sortOptions = new Sort("invalid",
							SortDirection.Asc,
							null,
							null);
 
sortOptions.SortBy = SortField.IdSortField;A possible better implementation would have been to use an enumeration of valid sortable field names.  That way, invalid values can't be passed in, and it would be caught at compile time instead of run time.

Valid Sort constructor call throws an ArgumentException

DvirLogs.Defects is marked as deprecated with the following message - "FB/289474 Need to support it at least for 1805, will be removing this after 1805".  Is this still accurate and if so, what is it being replaced with and when? 

Is DvirLogs.Defects still scheduled to be removed

page-user page-user-mdevol template-account-profile page-status-200 theme-harmony user-guest

Company

Title

Thanks for straightening me out. Apparently I didn't read down far enough in the documentation to find the C# example. Thanks for the help!

In GeoTab.Checkmate.ObjectModel ver. 11.118.421, the following valid Sort constructor call throws an ArgumentException:<code>Sort sortOptions = new Sort(SortField.IdSortField,
						 SortDirection.Asc,
						 null,
						 null);</code>This is because of a logic bug in the following Sort constructor code <code>	public Sort(string sortBy, SortDirection? direction = global::Geotab.Checkmate.ObjectModel.SortDirection.Asc, string? offset = null, Id? lastId = null)
	{
		if (SortField.ImplementedSortFields.Contains&lt;string&gt;(sortBy, StringComparer.InvariantCultureIgnoreCase))
		{
			throw new ArgumentException("Use existing implementation of ISort for this field");
		}
 
		SortBy = sortBy;
		SortDirection = direction;
		Offset = offset;
		LastId = lastId;
	}</code>In the if statement, SortField.ImplementedSortFields is a string array that contains all the valid sortBy field names, which means that the exception should only be thrown when Contains returns false. So, for this to work correctly, the return value of Contains should have been inverted, meanting the if statement should look lie this: <code>if (!SortField.ImplementedSortFields.Contains&lt;string&gt;(sortBy, StringComparer.InvariantCultureIgnoreCase))
{
	throw new ArgumentException("Use existing implementation of ISort for this field");
}</code>I've been able to work around this by passing an invalid sortBy value and then changing the SortBy property value <code>Sort sortOptions = new Sort("invalid",
							SortDirection.Asc,
							null,
							null);
 
sortOptions.SortBy = SortField.IdSortField;</code>A possible better implementation would have been to use an enumeration of valid sortable field names. That way, invalid values can't be passed in, and it would be caught at compile time instead of run time.

Thanks for the information, I'll check it out. The message if from your DVIRLog.cs file around line 89 (screenshot below). This is from Geotab.Checkmate.ObjectModel 11.118.42 <img src="/forum/plugins/gcs-uploads/files/069Pd000012WxjKIAS.png" alt="image" />

DvirLogs.Defects is marked as deprecated with the following message - "FB/289474 Need to support it at least for 1805, will be removing this after 1805". Is this still accurate and if so, what is it being replaced with and when?

Recent Activity

Getting PlatformNotSupportedException when authenticating to GeoTab

Valid Sort constructor call throws an ArgumentException

Is DvirLogs.Defects still scheduled to be removed