Symeon:
I ran into this problem with multiple version of UD and mv.NET. I don't
think it mattered which version off the ".dll" was used for mv.NET. Our
current production is on UD 7.1.9 and our development is on UD 7.2.5.
We use 2.1.1.7211 on our UD 7.1.9 server. We do, however, make dbms
connections with several other UD servers running 7.1.9 - 7.1.20. Our
new development environment uses 2.2.0.7276 running on Windows 2K8 R2,
connecting to a UD 7.2.5. This was the latest non-2K8R2 release (I
think). There should be a new 7.2A client, with a new "uodotnet.dll"
but I haven't been able to get it yet.
I've heard that there's a new UD 7.2.7-9 that resolves some issues with
Win 2K8-R2. I don't have that yet either.
HTH,
Bill
------------------------------------------------------------------------
Symeon Breen said the following on 8/6/2010 1:31 AM:
Hi - i am after a bit of advice from the group - i know it has been said
before to use the latest uniobjects .net dll but is that true regardless of
what udt version you have
i.e. i have one customer on udt 7.1.0 and they are using a dll at version
2.1.0.7137, I have another machine on the latest 7.1 - 7.1.15 and the
clients cd for this has the dll at version 2.1.2.7232, is it a good idea to
use this dll for the uo.net connections that go into the 7.1.0 machine ?
Thanks
Symeon.
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
