Unexpected error has occurred during the library compilation process: The assembly compilation returned the following errors: * Value of type 'String()' cannot be converted to 'File'. * Value of type 'File' cannot be converted to 'String()'

Help Studio
, , , ,
1

Hi everyone,

I’m encountering this compilation error when trying to publish my framework:

The assembly compilation returned the following errors:
 * Value of type 'String()' cannot be converted to 'File'.
 * Value of type 'String()' cannot be converted to 'File'.
 * Value of type 'File' cannot be converted to 'String()'.

image

The issue is: I’m not sure where in my process this type mismatch is happening.
My project is quite large, and manually checking every argument, variable, and activity isn’t very efficient.

Before I dig through the entire workflow step by step…

:red_question_mark: Is there a way to precisely locate which XAML, activity, or argument is causing this compilation error?

Ideally, I’m hoping there’s:

  • A log file that points to the specific XAML
  • A setting that enables detailed compilation diagnostics
  • Or any trick to instantly find which file contains the mismatched types

The error message doesn’t indicate where the problem occurs, so I’m wondering if there’s a method I’m not aware of.

Thanks in advance — would really appreciate any tips or best practices for tracing this!

— RetryScopeKid

2

@RetryScopeKid

Welcome to the community

specifically the error is regarding a string to file..so check the ilocalresource ot file type and string type arguments

if you are doing any file loops or so check there

cheers

3

@RetryScopeKid Try to check weather the error is highliting any xaml file name if available try to find any activity that accessing file path like for each file in folder etc, and also check if you are copying or renaming file activity is available

4

Hi @RetryScopeKid

image
image613×597 43.4 KB

run Workflow Analyzer manually.
For issues/conflicts — Analyzer will usually point to the file.