Installing Microsoft Graph package leads to errors

[pere]

I’m on a Microsoft Windows (non-legacy) project.

Installing Microsoft Graph 4.11.0 package, then updating to last version (5.34.0) causes an error and Main activity disappears; restarting Studio and reopening throws an error.

Only way to recover the project is to uninstall the package. Then if you want to use it stay on the 4.11 version and prevent from updating.

By the way, I don’t understand why the package manager is not offering to install the last available version from the beggining, then it shows up as a suggestion for upgrading.

[pere]

Various updates on the matter:

• Staying on the 4.11 version doesn’t show any activities when searching for “graph” in the Activities section.

• Upgrading to 5.34 throws the abovementioned error. Both in package manager you have the option to choose a lower version. Choosing 5.33 and downgrading to that one doesn’t produce an error, yet the Main.xaml won’t open.

[pere]

This is the error when upgrading to 5.34.0. Sometimes it just shows up and dissapears and it’s difficult to catch:

[pere]

I tried to downgrade to a bunch of lower 5.XX versions and all them threw the error; the highest one I could downgrade to was 4.54, yet no “graph” activities show up when searching.

[Jon_Smith]

So I’m guessing the WPF addin that is referenced is related to the Windows Presentation Foundation which is the framework that UiPath is built on that allows you to develop with low code building blocks, when it fails to load logically you also cannot load any workflows.

Regarding the error, firstly may I ask what you need the Graph API library for? I’m curious since I don’t know of any real use cases for it and wonder if perhaps you think you need it when you don’t.
Even if you do need it, there won’t be any activities for it in the activities pane no matter which version you use, this is a just a normal .net library, it won’t have any ‘Low Code’ activities that you can plug in.

Perhaps zoom out and describe what you want to do and why you think you need this package?

[alexandru (Alexandru Roman)]

We will improve the way Studio reacts for conflicts like this. By the way, you don’t need to import Graph, I see you already have 0365 package installed that will also bring the graph dependencies.

[pere]

Thanks @Jon_Smith ,

I was just trying packages, to see if I could accomplish my requeriments at a different “level” than the one or ones “provided” by UiPath (that don’t work for me). In my desperation I thought that, maybe, using this package I could “directly” have direct access at a lower level to the functionality that the Graph API provides, but sadly that’s not the case. I still wonder what this package is for and, if it’s not worth anything, why is it available for download.

@alexandru , with my previous statement I hope it’s clear for you now why I installed this package. Not as a mean of “importing Graph”. Just trying to figure out how to solve problems that UiPath createad by breaking compatibility in newer versions with things we had already working and for whose there are no alternatives.

[Jon_Smith]

@pere

I still wonder what this package is for and, if it’s not worth anything, why is it available for download.

Its not intended for use with UiPath, its just a normal .NET library you might use in Visual Studio when writing ‘High Code’.
Anything available on the nuget feeds for .NET is able to be imported into Studio, most will not have low code activities in them and you’d need to use them directly in code, either in a coded workflow or in an Invoke Method type situation.
It can be super useful to use some, but you can’t, for example, ‘inject’ the Graph API code into an existing low code activity if you dont like how it works.