Hi all,
Can anyone suggest the best practices in following Application Isolation for Wise. I have a situation where I need to make a choice in associating a dll to 2 exe's .Suppose if I've isolated dll using anyone of the exe to local directory, will the other exe refer to the same dll which got installed in the local directory or will it go and look in the system32 where the dll was earlier.

how does the application look for the dlls generally,is there any means to make the application refer to the local dll installed during application isolation instead of going to the shared directory.

thanks in advance.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


This is really dependent on the applications. For example .Net apps will look locally first and then to some place in %PATH%. But older applications may be hard coded to look in %PATH% and in that case there isn't much you can do. However, you may be able to have the dlls in separate locations and launch the applications with a batch file. Then inside the batch file set path, which will only count for that instance of the command window.

But it will just be trial an error unless it is a .Net app.
Answered 05/17/2007 by: yarborg
Blue Belt

Please log in to comment