I purchase your book in titled "Professional Visual Basic .Net Transactions" by Matthew Bortniker and James Conard. Its a very very nice book and Im very glad that you guys asked these 2 guys to write this book.
I want to ask some questions about COM+ Transactions.
Heres the scanario of my project:
I have a DLL made from VB
6.0 and VB
.Net and both have Transaction Support Attribute (TSA) as Required so I can benefit full services offered in COM+ such as Object Pooling, JIT and some other good stuffs.
Now, there is this 3rd party company who wrote an API for us for Cryptography and they uses Microsoft's CAPI (windows advapi32.dll) at the top of their API. My problem is - advapi32.dll from Microsoft and their API's DLL cannot be installed and registered in COM+ and Im worried about the scalability of my DLL that was being registered in COM+.
According to from your book on page 212 "Creating Subordinate Objects" - only those DLL that have TSA as Required can becomes part of the same transaction stream as the creator. Meaning the creator is my DLL and Microsoft's advapi32.dll and their DLL as the subordinate objects right?
So, what I understand here is my DLL will be using COM+ services while their DLL dont have those capabilities am I correct? Then who manages their threads and objects if COM+ wasnt doing the work for their DLL?
Please enlighten me about this matter.