Yes, we have been developing an entirely new product
with UO.NET and UV since June. Mostly it has worked
quite well, but we have hit a few snags.

With the beta version of uodotnet.dll we had a problem
with the GetArg or getArgDynArray methods on one
particular UniSubroutine object. It would sometimes
return garbage values for higher argument numbers
(above 5 or 6), or cause an abort with a message about
"possible client-side licensing problem." The
orkaround was to reduce the number of arguments. (We
combined several single-valued arguments into a
dynamic array.)

With build 1.1.7073.0 (first released build dated
7-Aug-04), we had these problems:

(1) LockRecord method of UniFile class raises
exception if record not found. But if executed twice,
it does NOT raise the exception the second time even
though the record is still not found. IMO, it should
not raise an exception, but I would be happy with any
consistent behavior.

(2) The UniVerse basic statement "DEL ATC<1>" causes
UO.NET to abort when ATC is an empty string passed in
to the subroutine as an argument. It is a UniDynArray
object in .NET. This happened every time in one
particular case, but it not occur with other
subroutines when they were passed an empty dynamic
array.

(3) The UniVerse basic statement"aMsg<-1>=Variable"
causes UO.NET to abort when aMsg is passed and it is
an empty string. Again, this happened every time in
one particular case, but not elsewhere.

My workaround for both (2) and (3) has been to insert
a statement like IF ATC="" THEN ATC="" for any
argument passed into a basic subroutine from .NET
where it might 
possibly be an empty string.

Yesterday, I installed build 1.1.1.0 dated 7-Oct-04
which patches a performance issue (not one that we
have experienced) with code like (example from Wally
Terhune 
at IBM U2 ATS):

uonetCMD.Command = "SSELECT CLIENTS"                 
uonetCMD.Execute()                     
uoSelectlist = uonetSession.CreateUniSelectList(0)    
 
Do While Not uoSelectlist.LastRecordRead
itemid = uoSelectlist.Next
Loop

So far, no new problems with this build. I have not
checked the issues with prior builds to see if they
are resolved in this new build.

HTH...

Regards, 

Steve Johnson
Technology Director
FXA Group Ltd.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]  
On Behalf Of Dave Tabor
Sent: Thursday, October 14, 2004 9:44 PM
To: [EMAIL PROTECTED]
Subject: [U2] Has anyone tried UniObjects for .NET?

Hi,

Just wondering if anyone has had a chance to try then
new UniObjects for .NET?  

If so:
What are your thoughts pro & con?  
Any bugs to keep in mind?  
Anything else?

Thanks in advance!
- Dave
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit
http://listserver.u2ug.org/
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to