What’s the best way to maintain communication between Visual Basic 6.0 and VB .NET applications when message queuing is involved?
The recommended solution when it is necessary to communicate between applications written in VB 6.0 and Visual Basic .NET is to keep the entire MSMQ communication layer consistent. For example, all of the application’s communication layer should be written in Visual Basic 6.0 or Visual Basic .NET. In such cases, it may be necessary to create new communication classes that will interact locally with components written in other languages. The COM+ Queued Components service provides an efficient way to invoke and execute components asynchronously using Message Queuing. Setting up this kind of processing can be done relatively easily by deriving the asynchronous class from System.EnterpriseServices.ServicedComponent.
Related Questions
- What’s the best way to maintain communication between Visual Basic 6.0 and VB .NET applications when message queuing is involved?
- I keep getting an error message The Visual Basic for Applications project is protected with a password - why?
- What is the best way to learn VBA ( Visual Basic for Applications) ?
