I am on studio 2023.10.9 and my manager code reviewed a small PR and noticed a load of .dll in the .local/install folder, I wasn’t able to tell him what they are for. Can someone explain their purpose? Thanks!!!
Can you share the exact folder path you are talking about?
I suppose @ewanc1 means DLLs in “projectfolder”.local\install which are created during project compilation.
Cheers
2 Likes
Exactly “projectfolder”.local\install
If you are talking about the DLL’s in the folder @J0ska said, those are complied version of your xaml files in the project which gets generated when we compile the project first time or whenever we make changes into the workflows.
Ideally you shouldn’t be pushing the .local folder to your repository at all because those will get generated automatically when someone clones the code and try debugging or running it.
These are safe to delete.
1 Like
In UiPath for the past few years they added various ways to load custom classes in workflows.
Some of these are, for example, via the dynamic activities.
The easiest one to explain is the cross platform document understanding ones, when you select a document type it will generate a class based on that document so you have strong typing on it.
The integration service also does it alot.
Lets say you have a Service Now connector that gets an object from Service Now, Studio will build a class based on that object in Service Now so you have strong data typing and these are all compiled into .dll’s
Coded workflows also leverage this functionality.
1 Like
Thanks people! We push packages to orchestrator via azure devops and deletion of .local causes it to fail, but I don’t know if that is specifically to do with the install folder.
It is, cause the classes you need are then gone, as I explained.
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.