Marco Hof

We recently noticed that using a single snap client instance in out VB.NET application from different threads exceptions during runtime. So we used to introduce the locking mechanism in our read- and write functions with the Synclock .. End Synclock statement. As locking variable we take "Me", so the actual current client instance of our wrapper class. And this seems to work. I have only read that it is not recommended to use the current class instance as locking variable because it is not performant...

Hello developers, I am using VB.NET for communicating with a Siemens plc. In most cases use of the client function DBRead succeeds, but sometimes it returns a huge value (e.g. the last time I received 3145728 as return value). Meanwhile I have extended my vb.net code by the function Client.ErrorText(Return_value) in order to to get a clearer message, but I have not run it yet. I have to mention that I call DBRead immediately after calling DBWrite related to the same DB and DW, so the same adress....