Hi Piotr,

>Is there a reason for not updating the version in current manifest file?

I just noticed that for gdiplus there were different versions living side by side in winsxs, and I thought that was the way to go? I don`t have enough knowledge of this stuff so if you could give answer what way to go it`d be nice

Regards

Op ma 9 mei 2022 om 11:30 schreef Louis Lenders <xerox.xerox2000x@gmail.com>:

https://bugs.winehq.org/show_bug.cgi?id=52975

Signed-off-by: Louis Lenders <xerox.xerox2000x@gmail.com>
---
dlls/msvcr80/msvcr80.rc | 3 +++
dlls/msvcr80/msvcr80_61.manifest | 7 +++++++
2 files changed, 10 insertions(+)
create mode 100644 dlls/msvcr80/msvcr80_61.manifest

diff --git a/dlls/msvcr80/msvcr80.rc b/dlls/msvcr80/msvcr80.rc
index 458c5df6f98..2d9f5457569 100644
--- a/dlls/msvcr80/msvcr80.rc
+++ b/dlls/msvcr80/msvcr80.rc
@@ -20,3 +20,6 @@

/* @makedep: msvcr80.manifest */
WINE_MANIFEST 24 msvcr80.manifest
+
+/* @makedep: msvcr80.manifest */
+WINE_MANIFEST61 24 msvcr80_61.manifest
diff --git a/dlls/msvcr80/msvcr80_61.manifest b/dlls/msvcr80/msvcr80_61.manifest
new file mode 100644
index 00000000000..4298d242046
--- /dev/null
+++ b/dlls/msvcr80/msvcr80_61.manifest
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
+ <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.6195" processorArchitecture="" publicKeyToken="1fc8b3b9a1e18e3b"/>
+ <file name="msvcr80.dll"/>
+ <file name="msvcp80.dll"/>
+ <file name="msvcm80.dll"/>
+</assembly>
--
2.36.0