DataMovement migration guide samples #47934
Conversation
|
API change check API changes are not detected in this pull request. |
jaschrep-msft
force-pushed
the
datamovement-migrationguide-samples
branch
from
792e671 to
723b03f
Compare
| ```csharp | ||
| // these values provided by your code | ||
| string filePath, blobUri; | ||
| LocalFilesStorageResourceProvider files; |
There was a problem hiding this comment.
can remove this line now and update below to be
LocalFilesStorageResourceProvider.FromFile(filePath)
There was a problem hiding this comment.
Same for the rest for FromDirectory as well
| { | ||
| BlobDirectoryPrefix = blobDirectoryPath, | ||
| })); | ||
| await operation.WaitForCompletionAsync(); |
There was a problem hiding this comment.
In track 1, does calling UploadDirectoryAsync, actually wait the entire transfer?
There was a problem hiding this comment.
as far as i can tell, it gives you a task for transfer completion. I don't know this for certain yet, but other things also don't make sense to me if i'm wrong
There was a problem hiding this comment.
From what I could tell when writing perf tests, it does. There is no other way to wait
|
|
||
| In the legacy data movement library, it was possible to check a report of how many files | ||
| were or were not transferred in a directory transfer, as shown below. This is no | ||
| longer supported in the modern library. Applications will need to enable progress reporting |
There was a problem hiding this comment.
Maybe instead of saying it's no longer supported, maybe something along the lines of in the modern library you have to opt-in and enable progress reporting through ProgressHandlerOptions to make it sound more like, we do support this scenario still, it just shows up very differently.
Side by side samples for common functionality in legacy vs modern Data Movement.