First time here?

You are looking at the most recent posts. You may also want to check out older archives. Please leave a comment, ask a question and consider subscribing to the latest posts via RSS or email. Thank you for visiting!

I ran into an interesting situation last week…the desire to access some of my Amazon S3 services from within a Silverlight application.

Amazon Simple Storage Solution (S3) is a pay service provided Amazon for object storage ‘in the cloud.’  Although there is no UI tool provided by Amazon to navigate your account in S3, a SOAP and REST API are available for developers to integrate S3 information into their applications or other uses.  You can view more information about Amazon S3 on their site.

What is S3?

Since S3 is a pretty flexible service, it can be used for many different things including storing “objects” like serialized representations of a type or something.  A lot of applications these days are using cloud storage to store their application objects like this.  For me, I use it as a file server in the cloud.  Mostly it is there to host my images on this site as well as downloads and such.  Because there is no user interface I collaborated with Aaron to make the S3 Browser for Live Writer so that I could access my files for when I need them in posting content.

Accessing content from S3 also has different meanings, even with regard to Silverlight.  For example, if you wanted to simply set an Image source to a hosted image on S3, you could easily do that using the URL provided by S3 to the object.  Since Silverlight allows media assets to be sourced from anywhere, this is not a problem.

The Problem

The problem comes when you want to download content in otherways, such as maybe a file stored there, a serialized object, or access their services in a Silverlight application.  Why is this a problem?  Well because S3 does not expose any cross-domain policy files in their implementation.  RIA platforms like Silverlight require a policy file from the providing service to exist in order to make cross-domain calls from the platform. 

You can read more about Silverlight’s cross-domain policy information here:


So how can we accomplish this?

The S3 Service APIs

Amazon exposes two service APIs: SOAP and REST.  Because of the requirements around using their REST service and providing an Authorization header, we are unable to use that in Silverlight at this time since Authorization is a restricted header we cannot modify at this time.  So we can use their SOAP service.  This is fine for Silverlight because Amazon provides a WSDL for us to generate a proxy with.  The defined endpoint in the WSDL for the service is https://s3.amazonaws.com/soap.  This is important so remember this.  Let’s move on.

Buckets to the rescue!

S3 uses a concept they call buckets to store information in containers.  I’m not going to into a lot of detail explaining this concept so if you want to learn more, read their documentation.  Basically a bucket is global unique to the service (not to your account)…so there can only exist one “timheuer” bucket across the service, name them accordingly :-).  All data you push to S3 must be in a bucket.  When you create a bucket, you can also access content in that bucket using a domain shortcut system.  For example when you create a bucket called “timheuer” and put a file in there called foo.txt, it has the URI of http://timheuer.s3.amazonaws.com/foo.txt.  Notice the alias that is happening here.  We can now use this method to solve some of our issues.  How?  Well the “/soap” key will be available at any bucket endpoint!

Because of this aliasing, we can use this mechanism to ‘trick’ the endpoint of our service to respond to the policy file request…so let’s review how we’ll do this.

Step 1: Create the bucket

There are different ways you could do this.  You could simply put a bucket called “foo” and use that, or you can completely alias a domain name.  I’m choosing to completely alias a domain name.  Here’s how I did it.  First I created a bucket called timheueraws.timheuer.com – yes that full name.  That’s a valid bucket name and you’ll see why I did the full one in a moment.

Step 2: Alias the domain

If you have control over your DNS, this is easy, if you don’t, you may want to use the simple bucket aliasing.  But I went into my DNS (I use dnsmadeeasy.com btw, and it rocks, you should use it too).  I added a CNAME record to my domain (timheuer.com):

   1: CNAME    timheueraws    timheueraws.timheuer.com.s3.amazonaws.com.    86400    

What does this mean?  Well any request to timheueraws.timheuer.com will essentially be made at timheueraws.timheuer.com.s3.amazonaws.com.  The last parameter is the TTL (time-to-live).

UPDATE: For security reasons you should actually stick with using only a bucket name and not a CNAME'd bucket.  This will enable you to use the SSL certificate from Amazon and make secure calls.  For example a bucket names "foo" could use https://foo.s3.amazonaws.com/soap as the endpoint.  This is highly adviseable.

Step 3: Create the clientaccesspolicy.xml file

Create the policy file and upload it to your bucket you created in step 1.  Be sure to set the access control list to allow ‘Everyone’ read permissions on it or you’ll have a problem even getting to it.

Creating the Silverlight application

Create a new Silverlight application using Visual Studio 2008.  You can get all the tools you need by visiting the Getting Started section of the Silverlight community site.  Once created let’s point out the key aspects of the application.

Create the Amazon service reference

In your Silverlight application, add a service reference.  The easiest way to do this by right-clicking on the Silverlight project in VS2008 and choosing Add Service Reference.  Then in the address area, specify the Amazon S3 WSDL location:

This will create the necessary proxy class code for us as well as a ServiceReferences.clientconfig file.

Write your Amazon code

Now for this simple purposes, let’s just list out all the buckets for our account.  There is an API method called “ListAllMyBuckets” that we’ll use.  Now Amazon requires a Signature element with every API call – it is essentially the authentication scheme.  The Signature is a hash of the request plus your Amazon secret key (something you should never share).  This can be confusing to some, so with the perusing of various code libraries on the Amazon doc areas, I came up with a simplified S3Helper to be able to do this Signature generation for us.

   1: public class S3Helper
   2: {
   3:     private const string AWS_ISO_FORMAT = "yyyy-MM-ddTHH:mm:ss.fffZ";
   4:     private const string AWS_ACTION = "AmazonS3";
   6:     public static DateTime GetDatestamp()
   7:     {
   8:         DateTime dteCurrentDateTime;
   9:         DateTime dteFriendlyDateTime;
  10:         dteCurrentDateTime = DateTime.Now;
  11:         dteFriendlyDateTime = new DateTime(dteCurrentDateTime.Year,
  12:             dteCurrentDateTime.Month, dteCurrentDateTime.Day,
  13:             dteCurrentDateTime.Hour, dteCurrentDateTime.Minute,
  14:             dteCurrentDateTime.Second,
  15:             dteCurrentDateTime.Millisecond, DateTimeKind.Local);
  16:         return dteFriendlyDateTime;
  17:     }
  19:     public static string GetIsoTimestamp(DateTime timeStamp)
  20:     {
  21:         string sISOtimeStamp;
  22:         sISOtimeStamp = timeStamp.ToUniversalTime().ToString(AWS_ISO_FORMAT, System.Globalization.CultureInfo.InvariantCulture);
  23:         return sISOtimeStamp;
  24:     }
  26:     public static string GenerateSignature(string secret, string S3Operation, DateTime timeStamp)
  27:     {
  28:         Encoding ae = new UTF8Encoding();
  29:         HMACSHA1 signature = new HMACSHA1(ae.GetBytes(secret));
  30:         string rawSignature = AWS_ACTION + S3Operation + GetIsoTimestamp(timeStamp);
  31:         string encodedSignature = Convert.ToBase64String(signature.ComputeHash(ae.GetBytes(rawSignature.ToCharArray())));
  33:         return encodedSignature;
  34:     }
  35: }

This will abstract that goop for us.

Let’s assume we have a ListBox in our Page.xaml file that we’re going to populate with our bucket names.  Mine looks like this:

   1: <ListBox x:Name="BucketList">
   2:     <ListBox.ItemTemplate>
   3:         <DataTemplate>
   4:             <TextBlock Text="{Binding Name}" />
   5:         </DataTemplate>
   6:     </ListBox.ItemTemplate>
   7: </ListBox>

So let’s just add a simple method to our Loaded event handler calling our ListAllMyBuckets method.  Remember, everything in Silverlight with regard to services is asynchronous, so we’re actually going to call ListAllMyBucketsAsync from our generated code.  We’ll need a completed event handler where we will put our binding code.  Here’s my complete code for both of these:

   1: void Page_Loaded(object sender, RoutedEventArgs e)
   2: {
   3:     DateTime timeStamp = S3Helper.GetDatestamp();
   5:     s3 = new AWS.AmazonS3Client();
   7:     s3.ListAllMyBucketsCompleted += new EventHandler<AWS.ListAllMyBucketsCompletedEventArgs>(s3_ListAllMyBucketsCompleted);
   8:     s3.ListAllMyBucketsAsync(AWS_AWS_ID, timeStamp, S3Helper.GenerateSignature(AWS_SECRET_KEY, "ListAllMyBuckets", timeStamp));
   9: }
  11: void s3_ListAllMyBucketsCompleted(object sender, AWS.ListAllMyBucketsCompletedEventArgs e)
  12: {
  13:     if (e.Error == null)
  14:     {
  15:         AWS.ListAllMyBucketsResult res = e.Result;
  16:         AWS.ListAllMyBucketsEntry[] buckets = res.Buckets;
  17:         BucketList.ItemsSource = buckets;
  18:     }
  19: }

The AWS_AWS_ID and AWS_SECRET_KEY are constants in my application that represent my access key and secret for my S3 account.  You’ll notice that in this snippet above the “s3” object isn’t typed – that is because I have a global that defines it (you can see it all in the code download).

So now if we run this application, we should expect to see our bucket list populated in our ListBox, right?  Wrong.  We get a few exceptions.  First, we get an error because we can’t find the cross-domain policy file.  Ah yes, remember we’re still using the Amazon SOAP endpoint.  We need to change that.

Changing the Amazon endpoint

You may notice that the SOAP endpoint for S3 is an https:// scheme.  We won’t be able to use that using this method because of our aliasing and the fact that the SSL certificate wouldn’t match our alias.  So we need to change our endpoint.  There are two ways we can do this.

We can change this in code and alter our code by creating a new BasicHttpBinding and EndpointAddress and passing them into the constructor of new AWS.AmazonS3Client().  But that would be putting our configuration in code.  Remember that when we added the service reference we were provided with a ServiceReferences.clientconfig file.  Open that up and check it out.  It provides all the configuration information for the endpoint.  Now we could just change a few things.  I decided to create a new <binding> node for my use rather than alter the others.  I called it “CustomAWS” and copied from the existing one that was there.  Now because the default endpoint for S3 is a secure transport and we cannot use that, we have to change the <security> node to mode=”None” so that we can use our custom endpoint URI.

The second thing we do is in the <client> node change the address attribute and the bindingConfiguration attribute (to match new new config we just created).  Mine now looks like this in entirety:

   1: <configuration>
   2:     <system.serviceModel>
   3:         <bindings>
   4:             <basicHttpBinding>
   5:                 <binding name="AmazonS3SoapBinding" maxBufferSize="65536" maxReceivedMessageSize="65536">
   6:                     <security mode="Transport" />
   7:                 </binding>
   8:                 <binding name="AmazonS3SoapBinding1" maxBufferSize="65536" maxReceivedMessageSize="65536">
   9:                     <security mode="None" />
  10:                 </binding>
  11:               <binding name="CustomAWS" maxBufferSize="65536" maxReceivedMessageSize="65536">
  12:                 <security mode="None" />
  13:               </binding>
  14:             </basicHttpBinding>
  15:         </bindings>
  16:         <client>
  17:             <endpoint address="http://timheueraws.timheuer.com/soap" binding="basicHttpBinding"
  18:                 bindingConfiguration="CustomAWS" contract="Amz.AWS.AmazonS3"
  19:                 name="AmazonS3" />
  20:         </client>
  21:     </system.serviceModel>
  22: </configuration>

Now when we run the application it will work and if we sniff the traffic we’ll see that the first request is to our clientaccesspolicy.xml file that enables us to continue with the /soap requests:

Now we can see a list of our buckets and after wiring up some other code so that when we click on the bucket, we’ll see a list of all the objects, bound to a DataGrid (details blurred for privacy) :


Sweet, we’re done!  We’ve now been able to provide our own clientaccesspolicy.xml file in a place where it didn’t exist before and be able to call the service.  We can now use other methods perhaps to create a new bucket, put objects in buckets, etc.

So in order to do this, we’ve:

    • Created an alias to an bucket in our S3 account
    • Uploaded a clientaccesspolicy.xml file to that bucket
    • Changed the endpoint configuration in our service reference
    • Called the services!

I’ve included all the files for the above solution in the download file.  You’ll have to provide your own access key/secret of course as well as specify the endpoint address in the ServiceReferences.clientconfig file.

Hope this helps!  Please read Part 2 of this post.

This work is licensed under a Creative Commons Attribution By license.

7/5/2008 1:25 PM | # re: Accessing Amazon S3 with Silverlight
Dude.. too spookey. Just started playing with S3 today. First question was how do i make it work with Silverlight.. did a search and you just blogged about it. You are the KING as ever :-)
7/5/2008 1:54 PM | # re: Accessing Amazon S3 with Silverlight
Excellent post! I was discouraged from using S3 when I learned about the lack of a cross-domain policy file from Amazon. This is a great work around.

7/5/2008 2:13 PM | # re: Accessing Amazon S3 with Silverlight
Great post (as usual)...
7/5/2008 8:42 PM | # re: Accessing Amazon S3 with Silverlight
Man, your posts are getting better and better. Thanks!

7/6/2008 8:13 AM | # re: Accessing Amazon S3 with Silverlight
Hi, Tim just wondering what tool you use to post the code in your blog posts?
7/6/2008 8:24 AM | # re: Accessing Amazon S3 with Silverlight
@Mark: I use the most awesome Live Writer (writer.live.com) as well as a free plugin (http://lvildosola.blogspot.com/2007/02/code-snippet-plugin-for-windows-live.html).
7/7/2008 5:56 AM | # re: Accessing Amazon S3 with Silverlight
Would something similar also work for the Amazon AWS Service?

Thanks for the interesting post!
7/7/2008 9:04 AM | # re: Accessing Amazon S3 with Silverlight

Excellent article and extremely useful. Unfortunately every time I try this I end up receiving a 404 error when the proxy tries to make calls to the service.

I can see via Fiddler that the ClientAccessPolicy.xml file is being found so it seems to be an issue with the SOAP Enpoint.

Any ideas?



7/7/2008 1:22 PM | # re: Accessing Amazon S3 with Silverlight
Turns out that although my ClientAccessPolicy.xml file was valid, something about it was stopping this from working. I copied Tim's file exactly and everything started working correctly.


7/8/2008 5:33 AM | # re: Accessing Amazon S3 with Silverlight
Hi Timheuer,
The I am able to access my files from the bucket, but i am not able to upload the file to the same bucket using silverlight. Same code works for a windows or web a application. Is there anything spl that i need to do for file upload from silverlight?

With regards,
7/8/2008 9:35 AM | # re: Accessing Amazon S3 with Silverlight
Hi Mubarak: I haven't tried uploading yet, perhaps you could send me your code and I can try to reproduce?
7/9/2008 8:09 PM | # why sl text always blurs?
off the topic:

why the font in silver light is always blurry especially when clear type is enabled. but, even I disabled smotth border setting in system, it still blurs. any solution to make it as sharp as other text in normal win apps?
7/10/2008 6:51 PM | # about why sl text is blurry
someone mentioned about it here:

This is a “feature” of WPF carried over into SL. It’s the #1 bug for WPF on Microsoft Connect:
I raised the issue with members of the graphics teams for WPF and SL last month at TechEd. Message I got from WPF: “we know, we’re working on it for post-SP1″. Message I got from SL: “it’s not important enough, we need to hear more complaints about it”.

let's all vote important for it to "force" the team fix the "bug" :)
7/11/2008 6:38 AM | # re: Accessing Amazon S3 with Silverlight
Here’s the code to perform an upload to S3 using the same helpers as discussed in this post:

// Show open file dialog to select the file to upload
OpenFileDialog = new OpenFileDialog { Multiselect = false, Filter = "All Files|*.*" };
// Ensure a file was selected
if (OpenFileDialog.SelectedFile == null)
// Read the file
var Stream = OpenFileDialog.SelectedFile.OpenRead();
// Set some UI elements
FileNameText.Text = OpenFileDialog.SelectedFile.Name;
FileSizeText.Text = Math.Floor((Stream.Length * 0.0009765625)) + "k";
// Popular Buffer
var buffer = new byte[Stream.Length];
Stream.Read(buffer, 0, (int)Stream.Length);
// Upload to S3 via Service
var s3 = new AmazonS3Client();
var timeStamp = S3Helper.GetDatestamp();
s3.PutObjectInlineCompleted += s3_PutObjectInlineCompleted;
// Set permissions
// Grant public access
var grants = new List<Grant>();
var group = new Group
URI = "http://acs.amazonaws.com/groups/global/AllUsers"
var grant = new Grant { Grantee = group, Permission = Permission.READ };
// Grant full access to yourself
var user = new AmazonCustomerByEmail { EmailAddress = "AWS_ACCOUNT_EMAIL_ADDRESS_HERE" };
var grant2 = new Grant { Grantee = user, Permission = Permission.FULL_CONTROL };
// Make the call
s3.PutObjectInlineAsync("BUCKET_NAME_HERE", FileName, null, buffer, buffer.Length, grants.ToArray(),
StorageClass.STANDARD, S3Helper.AWS_AWS_ID, timeStamp,
S3Helper.GenerateSignature(S3Helper.AWS_SECRET_KEY, "PutObjectInline", timeStamp),

Which is working well for me (I am on Win2k03 Server, IE7 or FF3), even when the Silverlight application is being hosted on another server. I am however getting some reports of errors from users using Vista who cannot complete the upload.

In this case the file is read into memory correctly (they can see the filesize displayed) but when the call to upload this via the service to S3 is made they get a HTTP 500 error from the service.

Still trying to work that one out!


7/14/2008 11:06 AM | # re: Accessing Amazon S3 with Silverlight
unruledboy: WPF uses ClearType which SL doesn't support. We are improving text rendering for both RTM as well as vNext of Silverlight.
7/16/2008 1:47 AM | # re: Accessing Amazon S3 with Silverlight
Quick Note:

If you're using the above code to perform uploads as well as downloads then you need to be aware that the:


call restricts you to files up to 1mg in size. See:


This presents us with an issue when trying to directly upload large files from Silverlight to S3. In the meantime I am using my server as a proxy for any files larger than 1mg and uploading them server side using ThreeSharp:


Obviously this is not ideal as if / when it scales then the proxy becomes a bottleneck.



7/18/2008 2:07 PM | # re: Accessing Amazon S3 with Silverlight
Very Cool! Great post!
12/3/2008 6:49 AM | # How to hanle XDomain Scenario in SilverLight 2 RTM?
We were using ExternalCallersFromCrossDomain=”FullAccess” in AppManifest.xml to handle cross domain scenario incase of Embed form. The “FullAccess” attribute has now been removed in silverlight 2 RTM. We need to find out some way to handle cross domain scenario for embedding silverlight xap in html page that is hosted on different domain.

Muhammad Javed
12/3/2008 8:32 AM | # re: Accessing Amazon S3 with Silverlight
Muhammad: There are still options for ExternalCallers property, just not complete full access. Scriptable is an option.
3/3/2009 5:50 PM | # re: Accessing Amazon S3 with Silverlight
One thing that caught me in using your samples is the fact that AWS is Case Sensitive. I had to learn to change both my bucket name and my ClientAccessPolicy.xml file to be all lower case before I was able to get the sample to work.

Eh, too much time spent writing C# in CamelCase I suppose...

Also, you might mention that S3Browse.Com is an excellent tool to use to both create the bucket and upload the client access policy file. I had to hunt around for a few tools before I found one that both let me browse/manipulate the files as well as set the public read permissions...
3/3/2009 6:46 PM | # re: Accessing Amazon S3 with Silverlight
Jay -- great point I did forget that :-). Also for tools I've started to use CloudBerry - http://www.cloudberrylab.com -- great tool.
3/18/2009 10:56 AM | # re: Accessing Amazon S3 with Silverlight
David, unfortunately right now Silverlight doesn't support the PUT verb yet.
4/1/2009 1:05 AM | # re: Accessing Amazon S3 with Silverlight
I have my media files (WMV)on amazon.com, when playing the files with a silverlight client, it is becoming a progressive download. I need to direct my request to Microsoft Media Server that do the connection to S3 Cloud. I did research couple of Converter of S3 to Drives, and tried to build publishing points on that drive with no luck. (S3Drive is a sample). Is there is a way to configure WMS to connect to Amazon S3 ?
4/1/2009 9:10 AM | # re: Accessing Amazon S3 with Silverlight
Ron I have not seen one, but can't imagine that being very efficient. If you have the WMS server anyway you should just use that.
4/4/2009 1:35 AM | # re: Accessing Amazon S3 with Silverlight
We have a big amount of files. So we are putting all the video files in S3. The WMS are EC2 machines. The API to get files from S3, are REST APIs like. While we do not want progrssive download for ht video files into the temp internet files, if we pass through WMV, it will be real video streaming...
The architecture is, silverlight player connect to WMS and WMS connect to S3. The whole S3 is not made for real video streaming, which is kinda a bummer for amazon S3. Is there a way for us to connect WMS with S3? do we need to develop a driver or something?
4/11/2009 8:51 PM | # re: Accessing Amazon S3 with Silverlight
Killer article man. Was looking into coding a Silerlight application to work with my S3 home videos and this article is gonna save me a lot of time!
9/6/2009 6:05 PM | # re: Accessing Amazon S3 with Silverlight
I'm updating my samples accessing Amazon APIs... even the ones that support cross-domain access have an issue, now that a signature is required.

Generating a signature on the client requires sending your secret to the client, and thats a problem - its no longer a secret, and there is no good solution with Silverlight apps (or RIAs in general). This hits you before the cross-domain limitations.
10/8/2009 5:54 PM | # re: Accessing Amazon S3 with Silverlight
I'm working on a solution for this now. The Secret is only needed to generate the signature. I'm building a web service on the server side to handle the signature generation. The web service requires the user to be authenticated before it will respond with the appropriate information. The Silverlight client app is only aware of the Access ID and not the Secret Key.

To add a bit of extra protection I'm going to do some assymetric encryption with a rolling key (RSA). The Silverlight App will generate a key pair for each request. The web service will also generate a new keypair for each request. The silverlight app will obtain a public key from the web service. It will then enrypt the known items minus the the secret key (which is only known by the server) and pass those back to the web service along with the public key generated by the SL app.

The web service will decrypt with its private key...generate the signature with an expiration, and encrypt with the SL app's public key before sending back. The SL app will then use the signature to make the request and discard it.

Using this method should provide a reasonable amount of security at the cost of a little extra overhead which I'm willing to live with. The private key for the SL app could still be discovered using a memory dump but since it generates a new keypair each time that shouldn't be a problem, and with the expiration method offered by S3, by the time someone extracts any useable information the signature should be invalid and a new one will be retrieved from the server.

On the server side the web service will maintain a list of used keys for each authenticated session and require a new key to be used each time. This way, even if someone were to be authenticated and gained access to the keypair they wouldn't be able to reuse it. They could generate their own keypair and make a request so I know it's not perfect...but this is about the best security scheme I could come up with (and the least I'm willing to live with) in order to authenticate to S3 using Silverlight.
4/2/2010 2:52 PM | # re: Accessing Amazon S3 with Silverlight
Thanks to the new features in Silverlight 4 I was able to build my uploader. I've written an uploader that supports large files and uploads directly to S3 without the use of a proxy server. However, I would highly recommend using a separate service to sign your requests to avoid storing your S3 Account information in the Silverlight control. I was able to upload various types of files and just completed testing with a 2.4 GB file. Big thank you to the awesome Silverlight team for responding to my feature requests and adding the needed functionality. :)
6/10/2011 5:24 AM | # re: Accessing Amazon S3 with Silverlight
I am trying this sample to access s3 bucket with this sample from Silverlight 4 application. Its throwing the following error message when it executes the following statment in code, {s3 = new AWS.AmazonS3Client();}. The error msg as follows,
"Could not find default endpoint element that references contract 'AWS.AmazonS3' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element.".

I have changed with my accesskey, security key. On the binding address, i used "http://<mybucketname>.s3.amazonaws.com/soap". I already set the access rights as public. Is there any obivious point am i missing here? Can someone help on this? Thanks in Advance. Ravindran Ramaraj.
6/15/2011 10:48 PM | # re: Accessing Amazon S3 with Silverlight
There is an article at a site that gives great insight to foundational elements when it comes to being able to successfully make money on the internet. RANGE ROVER HIRE LONDON

6/16/2011 4:00 AM | # re: Accessing Amazon S3 with Silverlight
This is good site to spent time on .I just stumbled upon your informative blog and wanted to say that I have really enjoyed reading your very well written blog posts. I will be your frequent visitor, that’s for sure. Affordable Advertising
6/30/2011 4:53 AM | # re: Accessing Amazon S3 with Silverlight
Sharing user experiences is often the best method for troubleshooting issues within software. Microsoft offers a constructive flow of communication through this blog- and for this we offer our gratitude...

7/8/2011 11:56 PM | # re: Accessing Amazon S3 with Silverlight
Nice information on this page. I would like to read more like this.Trucking Software
7/14/2011 12:34 AM | # re: Accessing Amazon S3 with Silverlight
I am always searching online for articles that can help me.Tarife vergleichen
7/15/2011 4:31 AM | # re: Accessing Amazon S3 with Silverlight
Hi.I really like your post.You have all you need for a writer,I mean writing skills and a lot of experience.I love your post,you are very good ,please don't stop writing.Thanks a lot.Private Investigations Austin
7/16/2011 5:06 AM | # re: Accessing Amazon S3 with Silverlight
thanks for you review and tutorial about how to comment.I think if we walk to other blog we most comment to give appreciate for owner. delicious healthy cookies

7/18/2011 12:10 AM | # re: Accessing Amazon S3 with Silverlight
Pretty nice post. I just stumbled upon your weblog and wished to say that I have really enjoyed surfing around your blog posts. In any case I’ll be subscribing to your feed and I hope you write again very soon.used car sales
7/18/2011 1:43 AM | # re: Accessing Amazon S3 with Silverlight
As a technical person i can easily understand the entire post. Your way of explanation is very good and keep writing such a latest information for us.car values
7/20/2011 1:10 AM | # re: Accessing Amazon S3 with Silverlight
Yes it appears that your website is a long time to load. You’ll need to chick with the webmaster that works on your website. Peridot Rings
7/21/2011 5:40 AM | # re: Accessing Amazon S3 with Silverlight
There is a social phenomenon underway: five generations are about to be working side by side.For over thirty years, the sheer size of the Baby Boomer generation defined the organization's social landscape, in a majority-rules cultural takeover.san diego carpentry contractor
10/20/2011 12:20 AM | # re: Accessing Amazon S3 with Silverlight
I must say this site is very informative..Thanks for sharing this site with us...
anti keylogger
4/10/2013 6:46 AM | # re: Accessing Amazon S3 with Silverlight
Thank you. I first started myself for WP8 but there were still some problems. Then I searched and found your blog; problems are gone!


Please add 3 and 4 and type the answer here:


The opinions/content expressed on this blog are provided "ASIS" with no warranties and are my own personal opinions/content (unless otherwise noted) and do not represent my employer's view in any way.