CloudDrive in SDK1.8 #136

Closed
xied75 opened this Issue Nov 29, 2012 · 5 comments

6 participants

@xied75

Half baked code leaving using CloudDrive very mess. In that you need to ref to the old StorageClient.dll, and bring in namespaces that will confuse compiler. Is there any plan to tidy up this?

@optimiz3

Strongly in favor of this being addressed, though it is more an issue with CloudDrive. Anyone linking to CloudDrive has to import both 2.0.2 and 1.7/1.8, which is a problem.

@maverix

Another Vote here.... I'm surprised there isn't more vocal noise on this issue.

@jeffwilcox
Microsoft Azure member

Closing as 1.8 release was long ago; for general feedback though please do use the UserVoice forums: http://feedback.windowsazure.com/forums/34192-windows-azure-feature-voting

@jeffwilcox jeffwilcox closed this Oct 17, 2013
@optimiz3
  1. The issue is still there regardless of version.
  2. Closing the issue because of a bug's title is pretty lame.
  3. At worst consider refiling the issue with a new title.
  4. Given that it's been more than a year consider:
    • Cutting cloud drive, and directing users to an old version so you don't have to support it
    • Separating out cloud drive into it's own release, independent of this module.

EDIT: I take it back, looks like CloudDrive was removed.

@jeffwilcox
Microsoft Azure member

I agree we dropped the ball here, still wanted to follow up as I was going through the issues for another project. Thanks for taking the time to respond though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment