Bug 560195

Summary: [Win32] Remove runtime assembly manifest activation
Product: [Eclipse Project] Platform Reporter: Nikita Nemkin <nikita>
Component: SWTAssignee: Nikita Nemkin <nikita>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3 CC: niraj.modi, rolf.theunissen, sravankumarl
Version: 4.15   
Target Milestone: ---   
Hardware: PC   
OS: Windows All   
See Also: https://git.eclipse.org/r/157775
https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/157775
https://bugs.eclipse.org/bugs/show_bug.cgi?id=570406
https://bugs.eclipse.org/bugs/show_bug.cgi?id=572262
Whiteboard:

Description Nikita Nemkin CLA 2020-02-16 09:29:36 EST 
Runtime assembly manifest activation is a very hacky workaround that isn't necessary anymore. Java executables (java.exe/javaw.exe) have correct manifests since at least Java 8.

Original code was added for bug 45918.
Comment 1 Eclipse Genie CLA 2020-02-16 09:33:21 EST 
New Gerrit change created: https://git.eclipse.org/r/157775
Comment 2 Rolf Theunissen CLA 2021-11-17 04:11:56 EST 
Please consider that SWT is a library, instead of depending on the manifest that is in a random executable, it should be fully self contained.

AFAIK, there should be support in the windows system to fully isolate a DLL that it is not depending on any configuration in the executable that it loads. That is, all the dependencies are specified by the DLL (including version), and nothing is assumed about the environment of the executable.
There is documentation about this, but cannot find it now quickly.

The runtime assembly activation might be a hack, but please consider to make SWT self contained.
Comment 4 Niraj Modi CLA 2022-03-04 00:01:30 EST 
Moving out of 4.23