ronen1n Posts: 21
5 days ago
|
I tried to update x64dbg but it looks like i need to delete Qt5Network.dll file Change log: "Get rid of Qt5Network dependency"
I found 2, one in release\x32 and one in release\x64
do i just add the following? DelFile release\x32\Qt5Network.dll DelFile release\x64\Qt5Network.dll
Is it need to stay future updates?
edited by ronen1n on 01/07/2025
|
|
link
|
Gianluca Administrator Posts: 1330
4 days ago
|
Hi ronen1n, Since we're on the forum here, I need to give the other users a bit of context.
----------------------------------- Ronen1n isn't talking about the x64dbg user-side update, that one works as usual. Since he's an SPS editor (one of the great people who make the entire SyMenu suite work!!), he's referring to the SPS update, i.e., the definitions that allow the suite's programs to auto-update. Ok, context provided. -----------------------------------
Yes, you can add the DelFile instruction in the "Script After Install" section of the SPS. Don't worry about the versions after this one because DelFile won’t throw an error if the Qt5Network.dll file doesn't exist anymore. Also, the DelFile should stay for a while, because we can’t be sure users are updating through every single version. For example, if a breaking change occurred between version 4 and 5, a user might skip directly from 4 to 8, so SyMenu still needs to delete Qt5Network.dll even if it normally shouldn't be there anymore.
Let me take this opportunity to explain another very useful technique for SPS. If a program tends to introduce breaking changes, you should use the "Clean Update" option. A clean update ensures that each version only contains the files included in the current package. However, in this case, you should preserve any configuration/data/customization files set by the user in the previous versions. For x64dbg, it looks like the only files to preserve are:
- release\x96dbg.ini
- release\x64\x64dbg.ini
The choice is on you.
BTW, a question for everyone: do you think it would be useful to create a new technical discussion area for SPS? I often speak privately with editors about the best practices for creating program definitions, but maybe it would be helpful to have these conversations publicly.
|
|
+1
link
|
ronen1n Posts: 21
4 days ago
|
If you create new discussion area for editors it will make the forum more organized but add confusion for some that used to ask in the general area and maybe make you add rules for opening new post and transfering posts that opened in the wrong place More simple way is to add something like "SPS Editor" in the post title or just live it like it is
In this app maybe some manually installed plugins also need to preserve on clean install Thank you for the good explanation
|
|
link
|
Gianluca Administrator Posts: 1330
4 days ago
|
You're right, plugins. As you already know, the "Ignore on Update" option can be used to skip single files or entire folders, so yes, you can add the plugins folder. I really like your idea of using topic categorization in the titles. Could you please update the title of this thread by adding "SPS Editor"? That way, we can kick off this new standard together.
|
|
link
|
ronen1n Posts: 21
4 days ago
|
Not sure what the format but I added it as [SPS Editor]
|
|
link
|
Gianluca Administrator Posts: 1330
4 days ago
|
Not sure if it's the best in absolute, but for me it is
|
|
+1
link
|