> Could you please let me know how you saw the policy redirected in
> msvcr80.dll 8.0.50727.163?
The policy file is:
C:\WINDOWS\WinSxS\Policies\x86_policy.8.0.Microsoft.VC80.CRT_1fc8b3b9a1
e18e3b_x-ww_77c24773
The file's contents were
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Copyright © 1981-2001 Microsoft Corporation -->
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
<assemblyIdentity type="win32-policy"
name="policy.8.0.Microsoft.VC80.CRT" version="8.0.50727.163"
processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC80.CRT"
processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>
<bindingRedirect oldVersion="8.0.41204.256-8.0.50608.0"
newVersion="8.0.50727.163"/>
<bindingRedirect oldVersion="8.0.50727.42"
newVersion="8.0.50727.163"/>
</dependentAssembly>
</dependency>
</assembly>
The second bindingRedirect redirects just version 8.0.50727.42 to
8.0.50727.163 but doesn't affect 8.0.50727.104. The .163 files are
dated 6/5/2006. The identical file is on my laptop.
I can send you a screen snapshot if you tell me what you would like it
to show.
Thanks
Mike
Charles Wang[MSFT] - 26 Sep 2007 11:34 GMT
Hi Mike,
Thanks for your response.
Now I am consulting this issue with our Dev team. The contents of the
policy redirections are just their want. Now this issue is in discussing
and I will get back to you as soon as possible when there is a final
confirmation. I appreicate your patience.
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
Charles Wang[MSFT] - 27 Sep 2007 08:01 GMT
Hi Mike,
I just got the confirmation from the Dev team. It is confirmed that this
issue was an older product issue and had been got fixed in the latest
service pack SP1. I think that that is why it started fine after you
installed SP1 redistributable.
They recommend that you redistribute VS2005 SP1 CRTs with your ActiveX
control so that this issue will not happen again.
Please feel free to let me know if you have any questions or concerns. Have
a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================