J
Johan Karlsson
Hi!
I have an application where the client call the server over .net remoting
(tcp).
The final code to be called looks something like this:
Public Sub Update()
Using t as New Transaction
UpdateThisObject()
UpdateChildObjects() ' <---
System.Transaction.TransactionException occurs here if remoted
t.Complete()
End Using
End Sub
I've setup a testcase that calls this code locally and remotely. The remote
call fails with a TransactionException whilst the local call succeeds. This
behavior is reproduceable within our development environment. I could try to
boil the code down to the smallest possible codebase to reproduce the error.
The underlying database is Sql Server 2005 on a remote computer. .net
framework 2.0.
Has anyone seen this behavior before?
Thanks
Johan
I have an application where the client call the server over .net remoting
(tcp).
The final code to be called looks something like this:
Public Sub Update()
Using t as New Transaction
UpdateThisObject()
UpdateChildObjects() ' <---
System.Transaction.TransactionException occurs here if remoted
t.Complete()
End Using
End Sub
I've setup a testcase that calls this code locally and remotely. The remote
call fails with a TransactionException whilst the local call succeeds. This
behavior is reproduceable within our development environment. I could try to
boil the code down to the smallest possible codebase to reproduce the error.
The underlying database is Sql Server 2005 on a remote computer. .net
framework 2.0.
Has anyone seen this behavior before?
Thanks
Johan