RE: Problem with side-by-side information



Hi,
I found a difference in the behaviour of different DLLs. The error in
Side-by-side information occurs for some DLLs with an embedded manifest like:

<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
<dependency>
<dependentAssembly>
<assemblyIdentity type='win32' name='Microsoft.VC80.CRT'
version='8.0.50727.762' processorArchitecture='x86'
publicKeyToken='1fc8b3b9a1e18e3b' />
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity type='win32' name='Microsoft.VC80.CRT'
version='8.0.50608.0' processorArchitecture='x86'
publicKeyToken='1fc8b3b9a1e18e3b' />
</dependentAssembly>
</dependency>
</assembly>

Here are two entries for a CRT library. These two entries are there for all
DLLs that also link a library that was compiled without SP1.
Other DLLs which don't link older libraries only have one entry for the CRT
in the embedded manifest.

Should one application now link different version of the CRT? I thought only
the newest version should be used?
Is there anything that can be done without having to get DLL versions
compiled with SP1 so that private assembies work?

Best regards
Markus


"Charles Wang[MSFT]" wrote:

Hi,
Thanks for your response.

The problem is that some CRT assemblies also changed in SP1 but for
side-by-side assemblies they always refer to the assemblies in the WinSxS
folder. Only if you use static link, the application could not work by
directly copying from one computer with VS2005 SP1 to another one without
it.

The solution is that you refer to the one of the two methods that I
provided to you in my first reply.

Hope this helps. Please feel free to let me know if you have any other
questions or concerns. Have a good day!


Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications

If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.


Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================
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.
======================================================






.



Relevant Pages

  • Re: Question about builds using Team Foundation Build Server
    ... Solution C contains 20 projects (4 exe and 16 dlls) Each of these projects references MANY of the dlls from Solutions A and B. ... (this step was done on the advice of MS Support on a paid incident) ... the reference path to DLLS not contained in the solution is all important. ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.vsnet.general)
  • RE: Vista / XP msvcrt.dll error
    ... create binaries with a dependency on Vista's msvcrt.dll. ... copied from a Vista machine to the problematic machine. ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.languages.vc)
  • RE: asp.net and dllimport
    ... unmanaged dlls). ... Microsoft MSDN Online Support Lead ... You can send feedback directly to my manager at: ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: msvcr71.dll and msvcr80.dll conflict?
    ... any objects or structs defined in the DLLs are potentially ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.vc.language)
  • RE: Partial caching (a UserControl) with file dependency
    ... As for the ASP.NET Output Cache, ... I've also check the FileDependency and the Dependency property you ... Microsoft MSDN Online Support Lead ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.framework.aspnet)