Messages
Reply
Edit
Delete03:53 pm
3S90Y261P
| From: | Rick Strahl |
| To: | ChaimCaron |
No that would work, but in general is a bad idea because as you note anytime you update your version those changes get blown away.
+++ Rick ---
Hi Rick,
I am making very good progress implementing the Client Tools v5.66. I am very close to being finished. Thanks for all your help.
I think this will be the last problem: I need to support two versions of Client Tools simultaneously because v5.66 won't run on Win/2K and I want to be able to run the new version (5.66) on my Win/XP machine. The two machines are on a network and the application is networked.
I am trying to figure out how to support multiple dlls at the same time which is tricky because dlls for different versions have the same name.
I have two ideas about how to do this:
1. changing the dll names: modify the dll name to specify the version and modify the source code accordingly. Then multiple versions of the dll could exist at the same time in one subdirectory. For example, I could change the name of the 5.66 dll to WWIPS566.dll. Could I then modify your source code to reference the correct dll?
I looked into wwSocket.prg and found statements like this:
DECLARE INTEGER wwSocketListen IN wwIPStuff.DLL
Would it work properly if I change all statements like this (in all relevant prg files) to
DECLARE INTEGER wwSocketListen IN WWIPS566.DLL
and then change the dll to the same name?
I understand that if I do this, and you issued an update, I would have to repeat the changes I made to the new version of the code.
2. your code finds the dll on the VFP path. I could control the VFP path depending on which version of the dll I want to use. If there are two dlls with the same name in different directories, both on the VFP path, which would your software use: the first one found or the last one found?
Are either of these approaches feasible? I prefer the 1st, changing the dll name, if it is possible to do this.
Thanks, Chaim
West Wind Technologies
Making waves on the Web