I publish a custom activity project, by right clicking xxxx.Design project → publish
and select to publish to a local folder. Then an error occured:
the diagnostic log is below:
5/9/2023 3:56:23 PM
System.AggregateException: One or more errors occurred. —> Microsoft.WebTools.Shared.Exceptions.WebToolsException: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details.
— End of inner exception stack trace —
—> (Inner Exception #0) Microsoft.WebTools.Shared.Exceptions.WebToolsException: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details. <—
Microsoft.WebTools.Shared.Exceptions.WebToolsException: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details.
This creates the nuget package for us and all thats left is to install it in UiPath and take it out for a test run!
I’m not 100% sure if this is the route we should take when publishing packages, but its an approach that worked for me.
We really need more tutorials/documentation on creating custom packages especially on 6.0 framework along with some of its best practices.
The examples I’ve seen on the UiPath Community YT channels are quite generic and don’t dive into any complexity. For example, when you are developing a package that involves UiPath variables like the ExtractionResults in document understanding(which you really shouldn’t be tampering around with) or the Taxonomy, we have to install the UiPath nugets as well if we are to see the namespaces populate in Visual Studio.
