Windows DLLs and path

[Bill Vlahos]

 Scott,

That's very clever to put them in a custom property and unpack when needed. I'm not installing into c:\Program Files so that should not be a problem.

How do you "free the dll"? Other than the dlls would still be there, is there a problem if a user uses the Task Manager to kill the program as it won't free the dlls?

Thanks,
Bill Vlahos

On Friday, May 25, 2007, at 08:06PM, "Scott Kane" <scott at cdroo.com> wrote:
>From: "Bill Vlahos" <bvlahos at mac.com>
>
>> Is there a way to tell the standalone they are in a subfolder?
>
>Possibly in Rev - but I've not tried it.  However...  It's normal practice 
>to place them in the standalone (executable) directory.  Placing them in the 
>path can cause dll hell in that another application uses a dll of the same 
>name or even a newer or older dll that your app can not handle.  So avoid 
>the path for this stuff.  In terms of the dll being in the same folder as 
>the standalone (executable) why not do something like this (providing you're 
>not installing into c:\Program Files which will cause problems in Vista):
>
>Put you dll into your standalone as a binary custom property.  When the app 
>executes unpack it to a file (.dll) and when your program exits delete the 
>dll.  This is pretty much what happens with some static linking programs 
>like C++, Delphi, VB etc.  You'd have to be sure to free the dll before 
>deletion.
>
>Scott Kane
>CD Too - Voice Overs Artist  &Original Game and Royalty Free Multi-Media 
>Music
>"Nothing is as powerful as an idea whose time has come."  Victor Hugo 
>
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-revolution
>
>