I have a situation that I need to solve where a .NET 1.1 application needs to integrate with a .NET 3.5 assembly.
- My first application is a .NET 1.1 CRM tool that allows me to insert standard .NET code.
- The second application is a third party CTI .NET 3.5 DLL that I have written a wrapper for to make it easier to use for our developers.
I know that I cannot link the 3.5 dll to the 1.1 application, so that option is out.....
My next thought is to use .NET remoting - I've been able to successfully create two applications and achieved some good results. My issue is that for me to use the entire wrapper class on both the .NET 1.1 side and the .NET 3.5 side is problematic
as I cannot link the 3rd party CTI DLL. I tried stripping the .NET 3.5 specifics (List<> operators and such) as well as removing any calls / references to the 3rd party DLL, but I get invalid SoapAction errors.
I'm not 100% sure I should continue down this path, especially since I have to gut so much of the wrapper DLL to get it all to work. At the end of the day, I need to be able to figure out some way to make my .NET 1.1 application perform the CTI
functions exposed by the 3rd party DLL. I'm pretty dependent on overloaded functions and some events.
After all this, my question is:
View Complete Post