14 minutes ago, Craig_Matthews wrote
If you're going by the MSDN link that was posted, the only resemblence to FTP is the arbitrary use of "anonymous" as a username. It looks like it sends the data to an upload.aspx page which is supposed to save the file. This functionality is nowhere near FTP. To follow the example of the MSDN link, the OP would need an upload.aspx on a web server listening for this request -- an upload.aspx which isn't explained at all by the posted MSDN link.
The My.Computer.Network.UploadFile method is a convenience wrapper around WebClient.UploadFile with some extra stuff like the ability to show a progress dialog. It uses either FTP or HTTP POST depending on the target URL. The documentation of the WebClient.UploadFile method fortunately does give an example of the server side page if you're using HTTP.
@JoshRoss: UploadFile has nothing to do with WCF, using a WCF service as the target URL wouldn't work. Also your sample is weird: hardcoded temp path (instead of using Path.GetTempPath), completely pointless use of a lambda (all it does is add unnecessary overhead), use of string.Format where Path.Combine is more appropriate, doesn't prevent escaping the temp directory (as you said).
I realize it's just a sample, but some adherence to good practice is generally advisable. Don't want to teach the newcomers bad habits, do we?