C# librarys (Pcwlx) and dll files
Hello,
I'm currently in quite a big project and we are working parallel with more people. Since we use Git this works quite well.
We make a big FB library in C# and want to use those in ladder in PLCNext Engineer. In the PLCNext solution we have 3 different projects, since the subjects are different. 2 of those 3 have to be build into a PCWLX file, the other one are just normal C# classes. Some files references to other ones, so we can make use of the classes for example
When building a PCWLX file, the binairy also contains some .dll files. I do understand that they are necessary. I was wondering if those .dll files also included in the PCWLX file? Because one of our programmers had to include the normal C# class in PLCNext Engineer, while the other one didn't have to. So we were wondering how is it updating everything? Is it building the pcwlx file of a normal C# class because we referenced to a program that is using IEC references? We want to know a little bit more about this, to set up a good project structure. Otherwise it's maybe better to make 1 project with a lot of files, because we otherwise have to update everything manually after every rebuild.
As I explained, it is quite easily to solve it with adding all user liberary's, even if it does not contain anything usable in PLCNext Engineer. But we just want to understand what is going on in the pcwlx files and the dll's
Thanks
Arne
I'm currently in quite a big project and we are working parallel with more people. Since we use Git this works quite well.
We make a big FB library in C# and want to use those in ladder in PLCNext Engineer. In the PLCNext solution we have 3 different projects, since the subjects are different. 2 of those 3 have to be build into a PCWLX file, the other one are just normal C# classes. Some files references to other ones, so we can make use of the classes for example
When building a PCWLX file, the binairy also contains some .dll files. I do understand that they are necessary. I was wondering if those .dll files also included in the PCWLX file? Because one of our programmers had to include the normal C# class in PLCNext Engineer, while the other one didn't have to. So we were wondering how is it updating everything? Is it building the pcwlx file of a normal C# class because we referenced to a program that is using IEC references? We want to know a little bit more about this, to set up a good project structure. Otherwise it's maybe better to make 1 project with a lot of files, because we otherwise have to update everything manually after every rebuild.
As I explained, it is quite easily to solve it with adding all user liberary's, even if it does not contain anything usable in PLCNext Engineer. But we just want to understand what is going on in the pcwlx files and the dll's
Thanks
Arne
Comments
Sorry for the delay. I have been around the houses trying to get a good answer for you, but unfortunately it is not great news.
There is currently no publicly available documentation on the structure of PLCnext Engineer libraries, or the relationship between these libraries and the dll's that you mentioned. In fact there are only a small number of developers here who really understand the details that you are looking for, and I am afraid that they are not currently able to share this information in a way that would be useful to you.
I understand that this information might help you to optimise your current (and future) projects. If the absence of this information is causing a more serious problem for you, then please let us know.
We hope that this information will be publicly available at some point in the future.
Regards,
Martin.
Thanks! I do understand the story. We changed the structure and got all of our files in one project file. So now we have no differences when using it, but we were curious why we had some difficulties and just wanted to know what was going on. So it's no problem at all! The connection between PLCNext Engineer and C# in Visual Studio works fine in general and I think it is a nice piece of technology! Glad to work with it.
Arne