When using the Media admin UI in the dashboard on the MediaPicker UI while the AzureFileSystem abstraction (which uses Azure Blob Storage) is in effect, one doesn't get far.
Exceptions occur for almost every operation. The cause is that paths are constructed with backslash separators instead of forward slash separators, and those paths are sent directly Azure Blob Storage which then reacts badly.
I think the MediaPicker and MediaService were initially smart enough to not assume a file system when it constructs relative paths. But somewhere along the way someone started assuming (making an ASS out of U and ME), and I guess nobody used CloudService deployment after that.
I have fixed this in AzureFileSystem by simply cleaning up any incoming relative paths supplied to it. Attached you will find the changed AzureFileSystem.cs file. I would like to have it included in the 1.x branch as soon as possible.
@DanielStolt created: https://orchard.codeplex.com/workitem/19503
When using the Media admin UI in the dashboard on the MediaPicker UI while the AzureFileSystem abstraction (which uses Azure Blob Storage) is in effect, one doesn't get far.
Exceptions occur for almost every operation. The cause is that paths are constructed with backslash separators instead of forward slash separators, and those paths are sent directly Azure Blob Storage which then reacts badly.
I think the MediaPicker and MediaService were initially smart enough to not assume a file system when it constructs relative paths. But somewhere along the way someone started assuming (making an ASS out of U and ME), and I guess nobody used CloudService deployment after that.
I have fixed this in AzureFileSystem by simply cleaning up any incoming relative paths supplied to it. Attached you will find the changed AzureFileSystem.cs file. I would like to have it included in the 1.x branch as soon as possible.