Thanks @marian.platonov! You might want to add this requirement here where it is stated that it requires only .net 6 while it seems that also .NET framework 4.6.1 is needed:
After the Visual Studio 2022 update to version 17.4.0, the extension is not working anymore.
The issue is with the publishing (see the image below)
Did you check the .tmp folder details?
Yes, I checked, but nothing relevant:
And the output message error from VS is:
The ‘Publish’ target is not supported without specifying a target framework. The current project targets multiple frameworks, you must specify the framework for the published application.
Yes, I have the same configuration:
I have 2 machines with VS2022. On the machine with an older version of VS 2022 everything is working well. More than that, I took a snapshot at virtual machine where I have the old version of VS 2022. After that, I updated the VS 2022 at the latest version. After the update, the publish is not working anymore. If I restored the machine to previous state, the extension is working well. I think is something related with an update of .Net Core from this new version
OK, this explain everything. What is your recommendation? To keep the VS 2022 at version 17.3 maximum? I suppose that the UiPath migration to the .Net 7.0 will not be in the near future.
Yes, keep VS 2022 at 17.3 in case you still need to use Activity Creator v4.0.
Would you know another workaround to fix the Extension besides downgrading the VS code.
My environment has some limitations regarding downgrading the VS code.
My issue happens even before publishing (and the same after), some dependencies are failing to be retrieved.
When using the latest version of VS code, you faced the same pattern?
I checked internally, and I was able to use Activity Creator v4 in a VS2022 17.4.1 version.
Regarding the missing dependencies, you may add extra feed sources. Check here Windows-legacy to Windows conversion: What about the Visual Studio made packages? - #8 by marian.platonov
In v3 I was able to build a NuGet package directly from publish, but in v4 it generates some dlls in the output folder.
My way of upgrading from legacy 4.6 to the new 6, was to create a new blank project and from there on create everything manually, making sure everything is .net 6 compatible.
My end result is this folder with dlls. How do I get this into a working nupkg?
I have found multiple guides, but none seems to work.
Last one stated the package should look like this:
But when importing it into UiPath, I get the error
Found the issue, I accidentally clicked the upgrade to Activities 6.0.3.
I have recreated the entire package from scratch and didn’t click the upgrade, and now it works!
Hi @mdiv how you recreated the entire package because I am facing the same error in NuGet package while adding the .dll file. Please help me in this.
Hi, I created the package from VS 2022.
As it is a blank project I went to NuGet Package Manager.
It is very important that you don’t upgrade these packages to 6.0.3.
I did that the first time and couldn’t get it to work, when I didn’t upgrade the second time, then it works.
I hope you can get yours to work!
Hi @mdiv Whenever I added any .dll file in NuGet Package it is showing these three errors I don’t know how to handle these errors. Can you please help me in this. Thankyou
Short guide to how I did it:
First create the lib by rightclicking the Package contents
Now rightclick the lib folder
Mark the new folder and click F2 to rename it:
Add your dll file(s) to the folder.
Go to your metadata (CTRL + K) and edit dependencies
Click the add groups, and name the target framework
As soon as you add the DLL file it will be red in health, but for me it still works.
It was a lot easier in the old Creator, that created the nuget package for me
Hi @mdiv Thankyou it is working fine now.
Hi @mdiv hope you are doing well. I am facing this issue when I am trying to run that custom activity. Can you please help me in this.?
Are you using VS 2022 to create your code? and the newest version of UiPath Activity Creator?
To me it seems like your using the old version since it request version 4.0.0 instead of 6.0.*