Correct way to access the physical disk (so i can plug in IFileSystem providers)
Hello,
I have been looking at a couple of problems people are having with uSync on things like azure, and i suspect most of them are because usync just uses System.IO stuff for managing the usync folder.
I know on azure that local storage, and blob storate and the like, aren't really.. well real, thats why the umbracoFile SystemProvider.Azure exists to fix media on azure. So ideally i would want to get usync using IFileSystem provider for all it's IO.
So question: What is the correct way to refactor System.IO sutff (like FileExistis, DirectoryExists, etc) to use IFileSystem providers so we can swap out the provider when moving something to azure?
(for more info its basically the calls in usync's IO helper class, and quite a few XElement.Load calls)
Correct way to access the physical disk (so i can plug in IFileSystem providers)
Hello,
I have been looking at a couple of problems people are having with uSync on things like azure, and i suspect most of them are because usync just uses System.IO stuff for managing the usync folder.
I know on azure that local storage, and blob storate and the like, aren't really.. well real, thats why the umbracoFile SystemProvider.Azure exists to fix media on azure. So ideally i would want to get usync using IFileSystem provider for all it's IO.
So question: What is the correct way to refactor System.IO sutff (like FileExistis, DirectoryExists, etc) to use IFileSystem providers so we can swap out the provider when moving something to azure?
(for more info its basically the calls in usync's IO helper class, and quite a few XElement.Load calls)
is working on a reply...