On 2010-09-08 22:09, Garrett Serack wrote:
Howdy,
GS> With the manifest in place, it will *not* try to load the DLLs from the
local directory (this is done to prohibit tampering of shared libraries).
Regis>But [1] says the searching sequence for the private assembly is:
Regis>
Regis> 1. S
Howdy,
Tim > Thanks for the explanation Garrett. I have some further
questions/comments below.
Tim >
Tim >So when Regis wrote:
Tim > "I checked manifest file in java.exe, CRT version is 8.0.50608.0,
Tim > but CRT dlls shipped with our build is 8.00.50727.42"
Tim >
Tim > that implies our buil
Howdy,
GS > With the manifest in place, it will *not* try to load the DLLs from the
local directory (this is done to prohibit tampering of shared libraries).
Regis >But [1] says the searching sequence for the private assembly is:
Regis >
Regis >1. Side-by-side searches the WinSxS folder.
Reg
On 2010-09-07 23:17, Garrett Serack wrote:
Howdy,
I can help out a bit here.
What you are seeing is the Windows Side-by-side technology at work here...
Unfortunately, the VC team didn't really use WinSxS the way they should, so
little issues like this tend to crop up all over the place.
Visu
Thanks for the explanation Garrett. I have some further
questions/comments below.
On 07/Sep/2010 16:17, Garrett Serack wrote:
> Howdy,
>
> I can help out a bit here.
>
> What you are seeing is the Windows Side-by-side technology at work
> here... Unfortunately, the VC team didn't really use Win
Howdy,
I can help out a bit here.
What you are seeing is the Windows Side-by-side technology at work here...
Unfortunately, the VC team didn't really use WinSxS the way they should, so
little issues like this tend to crop up all over the place.
Visual C++ automatically embeds information in th
