Hi Rick, I am finally installing the release card stuff you helped me with a while back. Worked fine in development but when try on live environment I get the above error. I have looked and none of the dll's are "BLOCKED". Any help greatly appreciated.

John Cook
828-461-8215

Make sure wwipstuff.dll is in your path... never seen any other reason for the DLL not to load.

+++ Rick ---

Hi Rick,

I have placed wwipstuff.dll, wwdotnetbridge.dll and freleasecardproxy.dll in the folder from which my app runs.

I should also mention, as long as I run the app from my development environment (the computer I work and compile on), everything works perfectly. It is only running it from the customer site that is causing these issues.

I got the error:

.NET Framework Initialization Error with error text being "To run this application, you must first install one of the following versions of .NET Framework: V4.0.30319 Contact your application publisher about obtaining the appropriate version of the .NET Framework".

It sounds like perhaps my proxy dll was compiled with .NET Version 4 but version 4 does not reside on the machine from which I am trying to run my app.

I did notice the call:

loProxy = CREATEOBJECT("fReleaseCardProxy","V4")

explicitly names Version 4. I tried changing it to V2 which IS on the workstation from which my app is running, but that did not work. I got the error: "Could not load file or assembly 'file:///c:\itf-test\freleasecardproxy.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. "
.... so now I am installing .NET Framework Version 4 on the workstation to see if that works.

Thanks,
John

Rick, I have just found out the following: For the release cards web services, they seem to have a URL for test and a different URL for production. When I use .net reflector, i see ws02-test.tponlinepay.com or something like that. I am not familiar with how the proxy generator works well enough to expand on this. Do I need to have you generate a different dll based on the url for production or something like that? I am quite confused and need help badly. Can you help me please?

Thanks,
John

You can change the URL dynamically in code by setting the service URL on the .NET proxy:

loBridge.SetProperty(loProxy.oService,"Url",lcNewUrl)

Also the cServiceUrl property initially determines the URL that is used, although that only applies when the service first loads.

+++ Rick ---