[DUG] Midas.dll

[Rohit Gupta]

David,

thats not what MS docs say, not that I believe everything in them.

You are correct that if you remove the folder that it was running from 
and then run something that requires it, and there isnt one in that 
exe's folder, it may spit the dummy.  But it will be someone elses app.  :-)

The gospel has always been - look in the exe directory first, then the 
system/system32.  Finally, and there is debate here - look in the 
path/libpath.  For a while now, the OS has supported multiple copies in 
memory.  Actually its a side-effect of the design, it cant do anything 
but.  :-)

Not only does it protect our app, its about the only simple way to 
deploy to Vista Workstations automatically from the server, without 
changing logins and permissions and access rights.

David Brennan wrote:
> Rohit,
>
> By my understanding this won't work reliably. I don't think there is any
> guarantee that Windows will use midas.dll from the executable directory. 
>
> The first time the midas library is requested Windows will search for
> midas.dll and during this search it will find it in the executable
> directory. From then on it will remember that it should ALWAYS look at that
> location for midas.dll. So if you delete that folder (and midas.dll) and
> then install your app (or another app) which requires midas.dll in another
> folder I believe Windows will spit the dummy and say it can't find
> midas.dll... even if you have included a copy in the new application folder.
> It is still looking for the one in the old folder.
>
> I wouldn't swear to it but that's my experience anyway.
>
> Cheers,
> David.
>
>
> -----Original Message-----
> From: delphi-bounces at delphi.org.nz [mailto:delphi-bounces at delphi.org.nz] On
> Behalf Of Rohit Gupta
> Sent: Wednesday, 3 October 2007 11:10 a.m.
> To: NZ Borland Developers Group - Delphi List
> Subject: Re: [DUG] Midas.dll
>
> I try to the keep the update size down for quick web updates, so every 
> possible external dll/bpl gets used.  We have only ever had one instance 
> where the exe required the new dll.  With the next release, all dlls and 
> bpls are now going to be in the exe directory.  And I was amazed the the 
> app compiled with D2007 carried on working when I had forgotten to 
> bundle the new midas.dll  Found it though, it was just XP hiding it. The 
> placing of the dlls also helps with Vista admin rights issue.
>
> Alfredo Ferrer wrote:
>   
>> Hi,
>>  
>> We used to deploy midas.dll separately in each client machine until 
>> after reading a similar article mentioned by Traci and yes, we got rid 
>> of this problem by simply adding "midaslib" to the project's  "uses" 
>> clause. We are using Delphi 7.
>>     
>
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at delphi.org.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at delphi.org.nz with Subject:
> unsubscribe
>
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at delphi.org.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at delphi.org.nz with Subject: unsubscribe
>
>