-
Notifications
You must be signed in to change notification settings - Fork 19
D26.RIO.10.3.2.4
Related: D26.RIO.10.3.2.0
This patch addresses the following issues:
In some situations, modifying a file in the IDE followed by making or compiling the project would not build the modified file into the resulting binary (RSP-25509, RSP-25590)
This issue would result in the built binary (such as your app) running, but not including the changes since the last time it was run. For C++Builder, this could include source code changes, such as modifications in a .cpp file. For Delphi, this would not affect modifications to source (.pas) files, but might affect other files such as resource (.res) files.
English, French, German and Japanese
Available only to registered users of RAD Studio, Delphi, C++Builder 10.3 and All-Access
MD5: 46EF1ABD56E7DB0E116683561233CCA2
Source link: https://cc.embarcadero.com/item/30889
The patch contains a .Net assembly. When downloading through Microsoft Edge and possibly other browsers, metadata is attached to the zip file that it was downloaded. This metadata persists when extracting the .zip using Explorer (it does not persist when using other tools, such as 7zip.) Because of that metadata tag, the .Net runtime will refuse to load the assembly, preventing RAD Studio from starting. You must remove this metadata before placing the DLL in the RAD Studio bin folder.
To do so, either:
Use a non-Explorer tool to unzip the patch, such as 7zip, or:
Before copying the DLL to the RAD Studio bin folder, right-click it and select Properties, then check the "Unblock" checkbox next to the warning that the file came from another computer.
If you don't do this, RAD Studio will not load and you will see an error message about loading an assembly, possibly followed by an access violation. This is caused by .Net not loading the assembly, and the IDE requiring it.