Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Not sure why you'd propose RDP. Aside from manual operation being required, you'd need to deploy your WinForms app with your deployment. A simple worker role running a straightforward task is simpler and can scale to multiple instances for faster performance.
    – David Makogon
    Commented Dec 20, 2011 at 21:39
  • 1
    Original poster specifically noted that he'd find it quicket to write a 'tool' than to write a worker role. Agree that I'd usually write a worker to do this but in this case I tried to provide an answer that paid heed to that constraint. You wouldn't need to deploy the WInForms app; literally you'd just drag it across the RDP link as you would connecting to and working with an on-premise server.
    – Chris J.T. Auld
    Commented Dec 21, 2011 at 5:07
  • Actually, I ended up doing pretty much that - copy-paste my WinForm into a running web role and run it from there. Even though it ran there, it was still not lightning-fast: it took about 22 hours to copy some 400,000 items (mostly medium-sized jpegs) - 46.5GB worth of data - I would have expected it to be much faster (no more than 5 hours).
    – David Airapetyan
    Commented Dec 23, 2011 at 20:33