Sorry.

Whatever Will said.

The trick is to use the bucket name WITHOUT slashes /bucketname/ or http: Instead, enter into AS the raw bucket name from your root AWS folder. AS structures a set of folders when it uploads. Mine looks like this:
/mentrepreneurs/0/activesocial/profiles/3/gallery/....

My bucket name is therefor: mentrepreneurs

Also from AWS:

To conform with DNS requirements, we recommend following these additional guidelines when creating buckets:

Bucket names should not contain underscores (_)

Bucket names should be between 3 and 63 characters long

Bucket names should not end with a dash

Bucket names cannot contain two, adjacent periods

Bucket names cannot contain dashes next to periods (e.g., "my-.bucket.com" and "my.-bucket" are invalid)

Not a bug, just a limitation in the Amazon API being used. We are planning to implement a different API in the next AS Feature release.


Is this "fixed" in the latest release?

Will, I'm looking for a better .NET S3 library myself, which do you recommend?

The latest SDK provided by Amazon is really good. If I were building my own project and not worried about distribution size I would use it. It is pretty large, but covers the full Amazon S3 API.

Posted By Frozen DNN on 11 Jan 2011 07:59 PM
Not a bug, just a limitation in the Amazon API being used. We are planning to implement a different API in the next AS Feature release.


Is this "fixed" in the latest release?

No, but should have the updated API very soon.  We have most of it done, but need to do more testing.

Posted By Will Morgenweck on 12 Jan 2011 05:27 PM

Posted By Frozen DNN on 11 Jan 2011 07:59 PM
Not a bug, just a limitation in the Amazon API being used. We are planning to implement a different API in the next AS Feature release.


Is this "fixed" in the latest release?

No, but should have the updated API very soon.  We have most of it done, but need to do more testing.

Is this "fixed" in the latest release?