Replies: 1 comment 2 replies
-
Due to the paths missing in the current metadata used in generating the SDK, this can achieved as var myDrive = await _graphClient
.Me
.Drive
.GetAsync();
var appFolder = await _graphClient
.Drives[myDrive.Id]
.Special["approot"]
.GetAsync();
var fileStream = await _graphClient
.Drives[myDrive.Id]
.Items[appFolder.Id]
.Children["salaries.db"]
.Content
.GetAsync(); |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
So I have a MAUI app that Reads and Writes a file to the users OneDrive App folder for my application. This all works fine using Microsoft.Graph 4.53.0 but when I update to version 5.12.0 everything breaks and will not compile for missing objects in 5.12.0.
An example is the code line "graphClient.Me.Drive.Special.AppRoot.Children" as the object "Special" no longer exists.
I did find the doc Microsoft Graph .NET SDK v5 changelog and upgrade guide but that doc does not help and does not talk about the users special App folder for his installed application to read and write files to.
So does anyone know if there is some migration document, web page, web site , or sample code some where that explains how to update and fix your code when migrating from 4.53.0 to 5.12.0?
Beta Was this translation helpful? Give feedback.
All reactions