Hi community,
I was wondering if we could develop faster by speeding up the publication of a c# script task used in a business process ?
I can debug it using Visual Studio but we can't really directly build in it to go faster. It is a real pain to wait every time I run the script to see if there are some errors or not.
Do you have some solution to this problem ? It would help me a lot.
I found how to debug the server side scripts on the academy but I did not found how to publish the scripts faster.
Many thanks,
Jonathan
Like
Hi Jonathan,
you can use either Clio with a Project package | Creatio Academy) or Assembly package | Creatio Academy, if you have a newer version (I think it was introduced in 7.18.3 or 7.18.4).
That will speed up the compilation process because not the whole configuration has to be compiled, but only the package you are working with.
However, read the docs carefully, because using these variants of configuration has some implications for the customizing and development later on.
BR,
Robert
Hi Jonathan,
you can use either Clio with a Project package | Creatio Academy) or Assembly package | Creatio Academy, if you have a newer version (I think it was introduced in 7.18.3 or 7.18.4).
That will speed up the compilation process because not the whole configuration has to be compiled, but only the package you are working with.
However, read the docs carefully, because using these variants of configuration has some implications for the customizing and development later on.
BR,
Robert
Robert Pordes,
Thanks for the reply. I knew about the initiation of a project package using Clio. However, if I am working, let's say on an existing business process and I want to modify it by inserting a new c# script task into it. I can't really create a new clio package only for that simple reason.
If doing like this, isn't there another way to compile / publish the c# script task and the business process faster ?
Hopefully I was clear enough in my explanation.
Let me know.
Best regards,
Jonathan
Hi Jonathan,
There is a task for our processes R&D team to make the compilation of the processes faster, but currently it's not possible to speed up the process using other ways than Robert presented. Also the publish speed depends on the number of lines in the code of the process - more lines, more time. The only thing I could propose here is using an assembly package that will not trigger all configuration compilation that will result in better publish speed.
Best regards,
Oscar
Oscar Dylan,
Okay, I see. Thanks a lot for the answer.
Best regards,
Jonathan