winsxs

Resolving C/C++ library version conflicts, mainly on Linux

南笙酒味 提交于 2021-01-27 20:30:36
问题 I have a situation more or less as illustrated here; it exists both on Windows and Linux, but I’ll draw it using Linux notation which is slightly clearer: libbar.so.1 and libbar.so.2 contain procedures with the same names and signatures but different behaviours. If I link the applications ‘naïvely’, then symbols from the library that is loaded last will ‘hide’ the ones from the one that is loaded first (at least, if I understand this reference correctly) and I have no way of using both

WinSxS: How to take dependency on specific version of gdiplus.dll?

北慕城南 提交于 2019-12-31 01:49:10
问题 I need to add a dependency on a specific version of GDIPlus. This is the version of GDI+ that i want: I want to be sure that I'm using this version for a specific compatibility reason. I've added an assembly manifest to my executable, defining my dependancy on the version of GdiPlus : <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.Windows.GdiPlus" pubicKeyToken="6595b64144ccf1df" version="5.1.3102.2180" processorArchitecture="x86" language="*" /> <

What files do I need to distribute as an alternative to MS Visual C++ 2005 ATL merge modules?

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-24 22:25:23
问题 Currently I'm distributing a software product that includes three merge modules: Microsoft_VC80_CRT_x86.msm ATL.msm policy_8_0_Microsoft_VC80_ATL_x86.msm Some customers use packaging technology that doesn't like these MSM files (I think because they have technical problems with them writing to WinSxS). Can I just distribute the dll files directly into my application's Program Files folder, and if so which dlls do I need? Is it just atl80.dll? 回答1: Your alternative is to run the VC_redist.exe

How to prevent embedded manifest from being used?

吃可爱长大的小学妹 提交于 2019-12-23 20:14:49
问题 I am working on many apps that uses RegFree COM Activation, everything works well except that one of the application is ran using an older technology that uses a JIT-type compiler. To get RegFree COM working, i have to provide a manifest to the launching executable (correct me if i'm wrong) with my dependencies listed. All my other applications are built in-house and i have full control over my manifest (authoring and if i embed it, if i leave it Side-By-Side, etc). But this JIT-compiler (ala

why i don't have Microsoft.VC80.MFC-file?

眉间皱痕 提交于 2019-12-23 10:28:30
问题 Got a fresh Win7 machine with VS2005 installed. I tried to start a MyApp.exe that is built with manifest that says in Manifest.bin: ... <assemblyIdentity type="win32" name="Microsoft.VC80.MFC" version="8.0.50727.4053" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"> </assemblyIdentity> ... and the result was error message "The application has failed to start because it's side-by-side configuration is incorrect... Event viewer told me the reason in detail: Activation context

GetFileVersionInfo() returns wrong file's version information

送分小仙女□ 提交于 2019-12-20 02:34:39
问题 I have an application that is required to check the versions of various system EXEs and DLLs to determine if they are vulnerable or not. This is a native C++ application which does not provide any specific WinSxS linkages in its manifest. On Windows 7, when I invoke GetFileVersionInfo on an absolute path, for example "c:\windows\system32\taskeng.exe", I receive the version information for "C:\Windows\winsxs\x86_microsoft-windows-taskscheduler-engine_31bf3856ad364e35_6.1.7600.16385_none

Unable to run debug build of application

末鹿安然 提交于 2019-12-10 19:13:09
问题 Visual Studio 2005, SP1 with Vista/Win7 update. The PC originally had VS 2010 installed but, since the rest of the team uses 2005, well, when in Rome... Initially, I installed 2005 and the updates and tried to build/run. Build ran fine, running (in debug mode) failed. So I uninstalled the VS updates, removed all versions of VS and associated components and reinstalled VS2005 with the SP and Win7 update. Same issue running in debug mode. I get a dialog telling me that the application config is

How to provide a private Side by Side manifest that correctly locates a .NET Dll as COM Provider?

*爱你&永不变心* 提交于 2019-12-10 12:29:25
问题 I'm researching about the configuration of a private registration free WinSxS with the plain provision of assembly manifest files, to stitch Delphi executables (COM clients) and .NET (C#) COM visible DLLs together at deployment and runtime. I already studied the documentation available at MSDN "Interoperating with Unmanaged Code", the sections about "COM Callable Wrapper" and "How to: Configure .NET Framework-Based COM Components for Registration-Free Activation" in particular. After even

How to cope with Install error 1920 about winsxs merge modules in Vista and 7?

半腔热情 提交于 2019-12-10 11:50:17
问题 When I try to install my msi package I get an error only in Vista and 7. "Error 1920. Service ... (...) failed to start. Verify that you have sufficent privileges to start system services" I get this error in Vista or 7 if I build my setup with C++ 9 CRT Winsxs MSM merge module If I use C and C++ 7 runtime libraries it doesn't have this problem, but I must build my exe with old versions of MS Visual Studio. Does anyone have idea how can I cope with that? 回答1: As a general rule of thumb, you

Can I modify the side-by-side assembly search sequence?

佐手、 提交于 2019-12-07 21:09:43
问题 I have a Windows, C++ software project (built with Visual Studio 2005, SP1) that has the following (simplified) file layout: {App. Root Directory} |-- bin | |-- Microsoft.VC80.CRT | +-- Microsoft.VC80.MFC +-- utils There are various executables that live in both the bin and utils directories. Each of these executables rely on the side-by-side assembly (C++ run-time DLLs) that we store in bin , but we have segregated them into these separate folders for various reasons (e.g., the exes in the