Renaming a file is creating a copy in dropbox .NET SDK

[SuryaMopuru]

When i try to rename file i see in dropbox a copy being created rather than just a name change.

This is how i am trying to achieve this:

using (var dbx = new DropboxClient(RefreshToken,Appkey,Appsecret))
{
var updated = await dbx.Files.UploadAsync(
"/" + remoteUrl,
mode:WriteMode.Overwrite.Instance,
body: fileStream);

remoteUrl: dropbox folder path. Ex: /Backup/Notes/

I have specified writemode as overwrite but still a duplicate is getting created rather than just renaming. Is there any way to handle this?

[Greg-DB]

The UploadAsync method is for uploading a file (whether a new file or a new version of an existing file). If you want to rename an existing file you should use MoveV2Async instead. That takes a fromPath for the existing path (including file name) of the existing file to move or rename, and toPath for the new path (including file name) that you want the file to have instead.

[SuryaMopuru]

How can i distinguish between rename and duplicate. Currently this is how i am trying to do:

 using (var dbx = new DropboxClient(RefreshToken, Appkey, Appsecret))
{
try
{
var metadata = (await dbx.Files.GetMetadataAsync("/" + backupItem.Path));
if (metadata != null)
{
var remote = "/" + remoteUrl;
var fromPath = "/" + backupItem.Path;
RelocationResult result = await dbx.Files.MoveV2Async(fromPath, remote);
if(result != null)
{
var updated = await dbx.Files.UploadAsync(
"/" + remoteUrl,
mode: WriteMode.Overwrite.Instance,
body: fileStream);
}
}
}
catch
{
var updated = await dbx.Files.UploadAsync(
"/" + remoteUrl,
mode: WriteMode.Overwrite.Instance,
body: fileStream);
} 

When i try to rename it is working because moveasync will get invoked but when i try to duplicate the file it is updating the existing file rather than duplicating it. Do we have any way to handle my scenario.

For the first time when user creates any file our GetMetadatAsync will throw an error because in the mentioned path we dont have file so it goes into catch block and upload the new file.

This should happen in duplication also.

[Greg-DB]

I see you also opened a new thread for this, so I'll follow up with you there.