Has anyone had the problem when building custom activities where Orchestrator always views the nuget package as Windows - Legacy 4.6.1? All the target frameworks in my solution are net6.0-windows, so I have no clue why this keeps happening. For others, what was missing that was causing this? I am using the custom activity template provided by UiPath.
Hey I figured out that original problem, thank you for your help. The whole reason I am making a custom activity is because I need to use a library. PDFTron for working with PDFs. For this library to work, it needs access to a couple of .dlls. This works fine when I am in studio but for it to work on Orchestrator I heard I need to put the dlls in a nuget package. Why is it that even when I include them in the nuget package, they are not able to be loaded at runtime. I checked my packed file and it has the two dlls I need with the project dll but it does not work when I try to use the custom activity in my actual project