I have a template which uses a custom NuGet built by our team. When I create a new project, the nuget needs to be renamed (the .NET solution is a part of the whole solution) so that each project has its own package with same base content, but extended as we see fit.
Once I build the renamed NuGet and add a reference to it and remove the reference from the template, UiPath loses ALL references to custom classes and every single argument/variable is replaced by String type and very often by Property instead of in/out, etc.
As a workaround I wanted to change the NuGet and then revert all the changes in xaml files in Git, so that the references come back, but for some reason while they are correct in xaml the Studio cannot compile the project and displays the replaced types. Example below.
How to mitigate it? I cannot ask all developers to go through the project each time and revert the changes manually. Thanks
1 Like
I’m not fully followed your exact methodology as I dont have the full details of how you are extending the base content from your nuget, but rather than messing around with trying to replace a renamed nuget package (which will always be problematic), have you considered using the newly available coded workflows?
You can still have your nuget with the base content and alot of abstract classes or virtual methods but then have concrete implementations of them in the coded workflows. In this manner you won’t need custom nugets and your workflows will already have the correct data types, you just need to complete the classes in the coded workflows in your template project.