I'm a bit confused. We are going to evaluate an automotive grade controller based on Codesys V3 as replacement for a Beckhoff PLC. Codesys stores the project as one single binary file so for Version control this is nasty. Especially while we work with several engineers on the same project you don't want to checkin blind risking to delete code of co-workers.
Can Codesys V3 save the project as single readable files only which can be compared for changes? Then we can use the normal SVN client we now also use for the TwinCat project.
If not, does the Codesys SVN package work nicely? It's reviews aren't very good and if we can't use Version Control, this would be a big showstopper for us. This should be for everyone so I don't get this...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Using an XML export should be a workaround but not the way we want to work.
It's strange to notice the difference between the industrial and the Microsoft oriented software world. In the Microsoft world, it is much more common to work with multiple developers on the same project
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm a bit confused. We are going to evaluate an automotive grade controller based on Codesys V3 as replacement for a Beckhoff PLC. Codesys stores the project as one single binary file so for Version control this is nasty. Especially while we work with several engineers on the same project you don't want to checkin blind risking to delete code of co-workers.
Can Codesys V3 save the project as single readable files only which can be compared for changes? Then we can use the normal SVN client we now also use for the TwinCat project.
If not, does the Codesys SVN package work nicely? It's reviews aren't very good and if we can't use Version Control, this would be a big showstopper for us. This should be for everyone so I don't get this...
CODESYS uses the SVN plugin in-house, so it cant be that bad, right? ;)
You could do a xml export and then use your normal svn client but to be honest the svn plugin works great in most cases.
And Git support is also in the making, but no ETA yet.
Best regards,
Marcel
Last edit: m.prestel 2020-12-03
Using an XML export should be a workaround but not the way we want to work.
It's strange to notice the difference between the industrial and the Microsoft oriented software world. In the Microsoft world, it is much more common to work with multiple developers on the same project