Storage Client Library for Windows Phone (Version 7.0)

Begins an asynchronous operation to append a file to an append blob. Recommended only for single-writer scenarios.

Namespace:   Microsoft.WindowsAzure.Storage.Blob
Assembly:  Microsoft.WindowsAzure.Storage (in Microsoft.WindowsAzure.Storage.dll)

Syntax

C#

Copy Code

 

[DoesServiceRequestAttribute]
public virtual ICancellableAsyncResult BeginAppendFromFile(
	string path,
	AsyncCallback callback,
	object state
)

C++

Copy Code

 

public:
[DoesServiceRequestAttribute]
virtual ICancellableAsyncResult^ BeginAppendFromFile(
	String^ path,
	AsyncCallback^ callback,
	Object^ state
)

F#

Copy Code

 

[<DoesServiceRequestAttribute>]
abstract BeginAppendFromFile : 
        path:string *
        callback:AsyncCallback *
        state:Object -> ICancellableAsyncResult
[<DoesServiceRequestAttribute>]
override BeginAppendFromFile : 
        path:string *
        callback:AsyncCallback *
        state:Object -> ICancellableAsyncResult

VB

Copy Code

 

<DoesServiceRequestAttribute>
Public Overridable Function BeginAppendFromFile (
	path As String,
	callback As AsyncCallback,
	state As Object
) As ICancellableAsyncResult

Parameters

path

Type: System.StringSystem::String^System.StringSystem.String

A string containing the file path providing the blob content.

callback

Type: System.AsyncCallbackSystem::AsyncCallback^System.AsyncCallbackSystem.AsyncCallback

An AsyncCallback delegate that will receive notification when the asynchronous operation completes.

state

Type: System.ObjectSystem::Object^System.ObjectSystem.Object

A user-defined object that will be passed to the callback delegate.

Return Value

Type: Microsoft.WindowsAzure.Storage.ICancellableAsyncResultMicrosoft.WindowsAzure.Storage::ICancellableAsyncResult^Microsoft.WindowsAzure.Storage.ICancellableAsyncResultMicrosoft.WindowsAzure.Storage.ICancellableAsyncResult

An ICancellableAsyncResult that references the asynchronous operation.

Remarks

Use this method only in single-writer scenarios. Internally, this method uses the append-offset conditional header to avoid duplicate blocks, which may cause problems in multiple-writer scenarios. If you have a single-writer scenario, see AbsorbConditionalErrorsOnRetryAbsorbConditionalErrorsOnRetryAbsorbConditionalErrorsOnRetryAbsorbConditionalErrorsOnRetry to determine whether setting this flag to true is acceptable for your scenario.

See Also

BeginAppendFromFile Overload
CloudAppendBlob Class
Microsoft.WindowsAzure.Storage.Blob Namespace

Return to top