Open with file explorer from anchor tag

This would be a killer feature. Hope it might happen. 

---

Tech Dev Oldsmar wrote:

This would be a killer feature. Hope it might happen. 

---

😁 Better don't rely too much. Not on the Dropbox at least.

"would be a killer feature": why would be? 🧐 it is actually. While Dropbox application is installed on your machine and works properly, the feature is available there. Dropbox application is listening on loopback ports 17600, 17601, and 17602 where any other application can connect and communicate to the application. That's exactly what Dropbox website does (or tries to at least) when you select on the site to send a command to open particular file/folder (and other commands).

It's another story that all available already features (the one mentioned within current thread and many other features too) are completely undocumented and so difficult to use. 😕 Such ideas are relevant to Dropbox application developers work, not to web API developers, unfortunately. Proven over time developers of the application are too lazy (just take a look on application release pages and try count word "lazy" in posts there from different users and not only) - just opposite of API (web by default) developers and support.

If you are DIY fan try be a man on the middle. 😉 Listen on 17600 (before Dropbox application launch) for websocks queries and forward them to 17601 for example (one to one). Log entire traffic and analyze it. In such a way you would be able catch and reproduce the pattern and perform proper queries to the Dropbox application through your own application while mimics the Dropbox web site. 🙂

Good luck.

This is exactly the kind of information I needed. I could not figure out what was going on inside the webpage trying to step through the click handler.

I realize after looking at network traffic it sends requests to the following:

https://www.dropbox.com/unity_connection_log

https://www.dropbox.com/unity_open_log 

The payload has a lot of variables that I'm not sure how I would get, but curious if anyone has been able to implement anything like this.

Maybe there is an easier way? I know Dropbox runs a program to actually open your file explorer window so maybe it would be easier to implement something that opened that program with the right parameters on your computer to open file explorer when you click a button that has the path. Some sort of browser extension maybe.

---

Tim Lempicki wrote:

... Any recommendations for tools to listen to these ports?

---

Hi Tim Lempicki,

There are lots of different tools to trace and evaluate particular connection of any kind. A typical example can be WireShark. Many tools availability is system dependent. If you have access to nc (or netcat), it's a very convenient tool for use in evaluation scripts too. Most of the programming languages (like Python) include in their standard libraries suitable tools. As such tools are countless, I (and not only) can't enumerate all of them, but hope above examples are good start point. 😉 Find what's most convenient to you.

Good luck.

Wondering if there is any further interest in supporting this feature through the API.  We use the API in production (which is rock solid, so thank you for a great product).  However, right now from the Intranet we open the DB folder then wait a bit for the context menu to show the "open in file explorer" to get to the local path.  This is a repetitive task so providing a direct link would net a lot of productivity.  

---

Tech Dev Oldsmar wrote:

...  This is a repetitive task so providing a direct link would net a lot of productivity.  

---

If the local path of Dropbox folder is only thing you're interested in, doesn't info.json work for you? 🤔 In spite opposite task (mapping local path to API path) example of something similar can be seen here. Just concatenate the two paths in your case (Dropbox folder path and relative file/folder path within) to produce the full path. 🤷

Tech Dev Oldsmar I don't have any news on the original feature request here. If the info.json that Здравко mentioned would be helpful though, you can find information on that here.

Thanks Greg - no problem with finding the local path...in fact, I have an Outlook Add-In that will automatically summarize the message body with OpenAI and archive the email into the proper DBX subdirectory based on a docket (e.g., ticket no).  The challenge is that modern browsers (wisely) do not support UNC paths to open File Explorer. Therefore, the little feature to open in File Explorer in the DBX web app is quite handy and I've hoped there would be motivation one day to support it through the API.  Just my two cents if it ever comes up in a meeting.  Thanks for closing the loop.  

I actually came up with a decent method of opening the Windows File Explorer having the synchronized DropBox files on the client from a website.  In this case, the website is running Blazor Server in .NET 7.  I create a SignalR Hub to which a small Windows Form application subscribes. 

using Microsoft.AspNetCore.SignalR.Client;
//replace localhost:7083 with your production URL
hubConnection1 = await ConnectToHub("https://localhost:7083/messageHub");

The website (using the DBX API) passes via SignalR the folder path and a userID to the Windows Form app. 

   var hubConnection = new HubConnectionBuilder()
       .WithUrl(url)
       .WithAutomaticReconnect()
       .Build();
   hubConnection.On<string, string>("ReceiveMessage", (message, userEmail) => 
// process received data from website....

The Windows Form app checks that the userID matches and then opens the path to the local DBX files:

 System.Diagnostics.Process.Start("explorer.exe", fullPath);

Because sometimes people install the DBX client in wacky places I also have a textbox in the Windows Form app that allows them to set the path to a Teams root folder (e.g., "C:\Users\userName\DropboxTeam\CompanyShare"

On the Blazor side:

@using Microsoft.AspNetCore.SignalR
// Link a method to a button click that calls:
 await HubContext.Clients.All.SendAsync("ReceiveMessage", dbxLocalPath, myUser.EmployeeEmail);
// in Program.cs don't forget:
using Microsoft.AspNetCore.SignalR;
builder.Services.AddSignalR();
app.MapHub<MessageHub>("/messageHub");
//Finally, make sure you have a Hub in your Blazor Server:
 public class MessageHub : Hub
 {
     public async Task SendMessage(string message)
     {
         await Clients.All.SendAsync("ReceiveMessage", message);
     }
 }

So the overall idea is that you have users with a little WinForm client receiving messages from BlazorServer to open file directories. Blazor sends a userID which you check matches the local WinForm client. Otherwise, all your users have File Explorer open when any one requests it from the website.