We make heavy use of internally developed libraries, which are often nested on multiple levels. I routinely work simultaneously on several libraries along with a project that use them. I make changes to a library and immediately perform a download (online or otherwise) in the project.
For the longest time, we had zero issue with this. But starting a good while back, with 3.5 SP19 I think, CODESYS started not noticing library updates in other instances most of the time. When the update is missed, the project sees no need to update the code, and any download ignores the new code. A "Clean all" does not solve the issue. But if I close and then re-open the project, then the new version is noticed and the download works.
The other solution is saving the library to the registry multiple times (say, 20-30 times, less if lucky), and then at some point the project notices the changed library.
I am now on SP21, and it is still not fixed. This is driving me mad, any tasks probably takes me double the time or more due to this problem. My colleague has the same problem on a separate computer.
Is this a known issue? Is there a setting somewhere that changes how updates are checked?
Thanks for any help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
tried this with SP22 P1 and I see no issues related to this. Can install the updated library in the repository, automatically get a message in my project that a new version is loaded and when I login, get a message to do an online change and see the new behaviour of the changes in my library.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just tried with version 3.5.22.1 and librarys updates often aren't recognized, usually not. Same behavior like 3.5.21.
To describe my workflow: one IDE is used to test librarys as project and two or more IDEs to edit librarys.
With only two open IDEs there is no problem, the problem began with more than two open IDEs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We make heavy use of internally developed libraries, which are often nested on multiple levels. I routinely work simultaneously on several libraries along with a project that use them. I make changes to a library and immediately perform a download (online or otherwise) in the project.
For the longest time, we had zero issue with this. But starting a good while back, with 3.5 SP19 I think, CODESYS started not noticing library updates in other instances most of the time. When the update is missed, the project sees no need to update the code, and any download ignores the new code. A "Clean all" does not solve the issue. But if I close and then re-open the project, then the new version is noticed and the download works.
The other solution is saving the library to the registry multiple times (say, 20-30 times, less if lucky), and then at some point the project notices the changed library.
I am now on SP21, and it is still not fixed. This is driving me mad, any tasks probably takes me double the time or more due to this problem. My colleague has the same problem on a separate computer.
Is this a known issue? Is there a setting somewhere that changes how updates are checked?
Thanks for any help!
Hello,
i got the same problem, but on my site it started with version 3.5.21,
with version 3.5.19.7 it worked like a charm.
How get the old behavior back?
Or how to reload the librarys in an open project/library manually?
Last edit: malie 2026-04-24
tried this with SP22 P1 and I see no issues related to this. Can install the updated library in the repository, automatically get a message in my project that a new version is loaded and when I login, get a message to do an online change and see the new behaviour of the changes in my library.
I just tried with version 3.5.22.1 and librarys updates often aren't recognized, usually not. Same behavior like 3.5.21.
To describe my workflow: one IDE is used to test librarys as project and two or more IDEs to edit librarys.
With only two open IDEs there is no problem, the problem began with more than two open IDEs.