Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Switching DLLS at execution/runtime

Status
Not open for further replies.

Chad123

Programmer
Apr 11, 2003
52
CA
Hello,

I was wondering if anyone knows how to do this? What I have is 2 versions of my dll (program.dll and program2.dll). Now what I want is to have them on a switch of some sort so that I (and my testing users) can run my program with the new code and have users execute the old one until I am ready to release to the masses. I can't use the #IF #ELSE #END IF statements because these are at compile time and I can't break all my other users. My compile directory is open and users can download updates anytime, so I can't leave a copy on there where they can get it.Besides it takes me at least 1/2 an hour (doing this twice does not appeal to me)

Now if I have to I can use a command line argument when the program is loaded, but I would prefer for it do be in an ini file on a switch.

Anyone with any ideas on how to do this?
 
Hey Chad,

I think I'm missing some of the big picture... What is the issue of having your users on Version 1 of the product with DLL 1, and having the test users on Version 2 with the DLL 2.



Craig, mailto:sander@cogeco.ca

In the computer industry, there are three kinds of lies:
lies, damn lies, and benchmarks.
 
Well, we have two sets of users: Testing and Production. We do not want the production users using the new version as we are still testing the "new" version of the product. Thus, we want to have all the test users use this "switch" for the new .dll and not have the production users affected by the change.
 
I am going to use the CreateObject() property to determine. Think it is a good idea?
 
Why not just give the test users the test version of your dll, and give the production users the production dll, you don't need different "versions" just different version "number" that you could set to autoincrement in the IDE. If you want, but i don't really see the need you can add a check for app.major, app.minor, and app.revision in your dll. So you could say dll.getVersion

And in the dll you have a function

Public function getVersion()as String
getVersion = app.major & "." & app.minor & "." app.revision
end funtion


Personally I don't see the need.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top