Craig Alvord

@RichardMSFT Getting a separate icon for symlinks should be pretty simple to do. But let's investigate for 1.35.0 what it would take to support navigation via symlink, and then we...

@richardMSFT Let's focus on getting symlink icons for the items in 1.36.0. Later we can look into implementing actual navigation for symlinks (#8112).

@bakoontz2 Since you replied, we'll just reopen this issue. We can repurpose the new feature request you made for implementing the symlink navigation feature.

We have several spots in the app that allow you to select encodings. Could be useful to have a generic "binary field" of sorts that lets you toggle the encoding...

Let's investigate to see whether this is feasible. At the very least, we may be able to add an encoding selector for text preview. We can add auto-detection afterwards.

Auto-detection turned out to be easy, very similar to how we do it for CSV/tabular data. We'll have this as well as an encoding selector for text preview.

@eliaquimbrandao Can you verify that the start and expiry times are reasonable? Can you try a SAS with an expiry time further in the future? Does a SAS generated from...

@eliaquimbrandao > However, if I don't want to connect my entire subscription to ASE, I need to relay in Azure portal to create my SAS to connect, what only for...

The error message says, "signature not well formed", which suggests the error was introduced in the creation of the SAS. I think it's likely the permission differences could be the...

@eliaquimbrandao Have you been able to resolve your issue?