I have this transaction in a separate .DLL which is called both from a WPF app and from ASP.NET MVC. It calles two separate stored procedures in two separate databases on the same server.
Somehow the WPF app doesn't need DTC to do that while the ASP.NET MVC app does. ASP.NET MVC gives me this error: The transaction manager has disabled its support for remote/network transactions.
How comes the WPF app doesn't need DTC while the ASP.NET MVC app does and is there a way to avoid it?
I simply circumvented the problem now by making a stored procedure on my main database that forwards the call (ie. directly calls) the stored procedure in my secondary database. It's an acceptable design choice as the SP in my secondary database should have been in my main database to begin with, but it's there because of legacy AND this solution totally prevents MSDTC escalation so it's much more nice than having to enable that whole circuit for just this one call (in our whole system).