>>I have written an app that runs DB2 on an AS400 via C#. We are upgrading our client machines with a DB2 client V6R1 throughout the enterprise. My C# middleware DLL references a DLL called IBM.Data.DB2.iSereies.dll. Unfortunately, the old and new versions of this DLL don't play well together - I read a piece on the internet that suggested I recompile the C# app with the new version of the IBM dll to make it work. This works for a local station with the new client, but not on the old.
>>
>>The problem is now I have two versions of my C# dll,m old client and new client. Is there a way for it to 'see' what version the client is running (old or new) and utilize the appropriate IBM dll at runtime? Maybe late binding or something? I don't know how to recompile the app and still use one of two possible dlls in code. First prize, of course, would be to not rewrite any code (or at least as little as possible)
>>
>>Thanks for your help.
>
>Irv,
>
>Take a look at message# 1250223 and the rest of the thread for some ways to do this.
>
>There is a VB version of instantiating an object at runtime. I believe there were some C# ideas also discussed in the thread.
>
>
>HTH,
>Bruce
bruce,

Thanks for your help this is a good thread discussing similar issues. The approach looks like late binding. I wouldn't mind this idea if I were just starting out writing my middleware DLL but it is already written with standard early binding. I was trying to avoid a lot of code changes.

Irv.