Studio Enterprise STS 2025.0.161 Doesn't Compile Unreferenced Workflows

Feedback Studio
, , ,
1

This version of Studio seems to skip compiling the workflows which aren’t referenced from visual workflows (both visual workflows and coded workflows are affected by this).

This means that when debugging, getting up to the part where one of these unreferenced workflows is used, an exception is thrown as the DLL is missing.

I have found this when both running and in debug mode.

I have switched back to LTS to avoid this but wanted to raise it with the hope that it doesn’t make it into the next LTS release.

3

Hi @matt.theisen

Unreferenced workflows are not compiled so DLL is missing at runtime causing error. Add all workflows directly or switch to LTS version to avoid.
Happy Automation

4

Hi @prashant1603765

What do you mean by ‘add all workflows directly’.

Do you mean switch back to the XAML visual workflows?

We have some rather large projects which use coded workflows so this is not realistic for us.

5

@matt.theisen
I mean making sure that every workflow, whether visual or coded, is explicitly referenced in your project. This ensures they get compiled properly, avoiding the missing DLL issue. You don’t need to switch to XAML workflows, just ensure all workflows are properly included and referenced in the project.

6

hello @matt.theisen ,
Thank you for raising this, can you please share:

  • error message you get
  • UiPathDiagnostic Tool output and sample project
  • sample project or steps to replicate

I tried replicating this internally but couldn’t.

Tried with invoking a file using a variable and the dlls are generated.
If the file is never referenced anywhere, then indeed the dlls are not generated, but also that file is never used in the automation and I don’t get any error.

Not sure how you end up in this situation. Is the file references in the automation another way?

when debugging, getting up to the part where one of these unreferenced workflows is used, an exception is thrown as the DLL is missing

image
image3834×2304 418 KB

Thank you,
Alex Bizon

7

@Alexandru_Bizon I think he’s suggesting that workflows that are ONLY referenced from coded workflows are being skipped in the compile.

In your example you are doing the opposite, referencing coded workflows from what he is calling a ‘visual workflow’.

Try it the other way around, have a coded workflow reference another coded workflow, with that being the single reference to that workflow, aswell as a coded workflow invoking a ‘normal’ workflow.

At that point his explanation makes sense to me.

1 Like
8

still no luck replicating.
@matt.theisen when you get the chance let us know the steps to replicate

Thank You

1 Like