Skip to main content
We are building an Net 6 API using UODOTNET to interface with a UNIDATA.
we are using version 3.171.0.08 of the library dated 9-14-2016

Data is coming back but  the value and attribute marks are using the same value and it seems to be a wide char value 65533 instead of the regular 253, 254.

Code snipit:


debugger output:

Is there a newer version available(UODOTNET)?
Has anybody dealt with this before?

Thanks in advance for any assistence wih this matter.

Dave Just Dave
We are building an Net 6 API using UODOTNET to interface with a UNIDATA.
we are using version 3.171.0.08 of the library dated 9-14-2016

Data is coming back but  the value and attribute marks are using the same value and it seems to be a wide char value 65533 instead of the regular 253, 254.

Code snipit:


debugger output:

Is there a newer version available(UODOTNET)?
Has anybody dealt with this before?

Thanks in advance for any assistence wih this matter.

Dave Just Dave
Dave,

There is a newer version of UODOTNET the file version I have is 3.171.1.9003 and Date Stamp of 01-21-2020
We also recommend that you now use U2ToolKit for .NET the latest version being 2.2.2.3502 released in 2021.
Also what version of UniData are you connecting to ?

I can't recall seeing this problem or having seen anyone report it.  When I get a free cycle or two I will test internally to see if we see the same problem.

Regards,
We are building an Net 6 API using UODOTNET to interface with a UNIDATA.
we are using version 3.171.0.08 of the library dated 9-14-2016

Data is coming back but  the value and attribute marks are using the same value and it seems to be a wide char value 65533 instead of the regular 253, 254.

Code snipit:


debugger output:

Is there a newer version available(UODOTNET)?
Has anybody dealt with this before?

Thanks in advance for any assistence wih this matter.

Dave Just Dave
Thank you for your response Jonathon.
We are using Version 8.1 of Unidata.

Can you provide a source or link for downloading the newer version of UODOTNET?
We are building an Net 6 API using UODOTNET to interface with a UNIDATA.
we are using version 3.171.0.08 of the library dated 9-14-2016

Data is coming back but  the value and attribute marks are using the same value and it seems to be a wide char value 65533 instead of the regular 253, 254.

Code snipit:


debugger output:

Is there a newer version available(UODOTNET)?
Has anybody dealt with this before?

Thanks in advance for any assistence wih this matter.

Dave Just Dave
Dave,

Login to RBC and go to https://rbc.rocketsoftware.com/matrix.asp from there you should be able to download the latest version of the U2 Clients which includes the driver. You should also be able to access the Toolkit as well.
We are building an Net 6 API using UODOTNET to interface with a UNIDATA.
we are using version 3.171.0.08 of the library dated 9-14-2016

Data is coming back but  the value and attribute marks are using the same value and it seems to be a wide char value 65533 instead of the regular 253, 254.

Code snipit:


debugger output:

Is there a newer version available(UODOTNET)?
Has anybody dealt with this before?

Thanks in advance for any assistence wih this matter.

Dave Just Dave
There is one UniObjects for .NET Driver Standard 2.0 (1.0.0) driver is from U2 5.2.1 client. It is better version working on .Net 6 environment. There is another similar version is released at 12/16/2021 for the U2 Toolkit .NET Provider 2.2.3. It supports .NET standard 2.0.
We are building an Net 6 API using UODOTNET to interface with a UNIDATA.
we are using version 3.171.0.08 of the library dated 9-14-2016

Data is coming back but  the value and attribute marks are using the same value and it seems to be a wide char value 65533 instead of the regular 253, 254.

Code snipit:


debugger output:

Is there a newer version available(UODOTNET)?
Has anybody dealt with this before?

Thanks in advance for any assistence wih this matter.

Dave Just Dave

It might be little too late but this is an encoding issue I've gotten before. How I resolved this was to add "ISO-8859-1" to my UOEncoding property that forms part of UniSession

Terms & ConditionsAccessibility statement