Hey guys,

I'm having a little trouble with shipping and billing addresses. I've successfuly pulled the correct shipping address from within my Checkout pipeline tasks - once when doing my CalculateShippingPrice, and once when connecting with warehousing.

In my CalculateShippingPrice method in my IShippingMethodService, I simply used the UCommerce.Entities.Shipment that gets passed to that method. From my understanding, UCommerce has already created this object for me, and I'm able to use:

shipment.OrderAddresses.Single()

which correctly pulls out the shipping address if there is one, or uses the billing address if not. I don't know how that works, it just does seem to. Either way, the IQueryable<OrderAddress> seems to only contain one element which is why I'm using Single()

Confusingly, things seem to be slightly different when I get the shipping address to connect with warehousing, which I'm doing in a custom pipeline task at the end of the checkout pipeline:

public PipelineExecutionResult Execute(PurchaseOrder order) 
{
    OrderAddress address1 = order.OrderAddresses.ToList()[0];
    OrderAddress address2 = order.OrderAddresses.ToList()[1];

    string billingPostcode = address1.PostalCode;
    string shippingPostcode = address2.PostalCode;
}

For whatever reason, in here, the shipping address is always the second element of the PurchaseOrder.OrderAddresses, and the billing address is always the first. I don't really get it, but whatever. It makes more sense here, but it makes the shipment.OrderAddresses from before seem weird - seems like a Shipment object should have a single OrderAddress element (called ShippingAddress), and a PurchaseOrder should have two elements (BillingAddress and ShippingAddress, rather than this IQueryable mystery thing).

Things get more hazy when I try and pull Shipping addresses from anywhere outside of the Checkout pipeline - in other words, in contexts where a Shipment or a PurchaseOrder haven't been explicitly passed to me:

protected void Page_Load(object sender, EventArgs e)
{
    Basket b = SiteContext.Current.OrderContext.GetBasket();
    Response.Write(b.PurchaseOrder.OrderAddresses.Count());
 }

I've used the UCommerce.Runtime.SiteContext to get the Basket. Maybe this is wrong. But I'm doing this in the page after the user has put in their Billing and/or Shipping addresses. Thus uCommerce has that data.

So I'm simply trying to display via a macro to the user their shipping costs based on products, postcode surcharges etc. I can calculate those fine within the IShippingMethodService, but I just can't display them on a page because I can't figure out how to get their shipping postcode.

Using the code above, the Response.Write prints out a huge number, like 20 (I'm guessing this is related to the number of times I've gone back and messed with my address information).

So I have three questions here:

1) Can you see any problems with the way I'm pulling billing/shipping addresses in the first two instances?

2) Am I missing something regarding confusing use of these various objects use IQueryable<OrderAddress> properties for all these addresses, or is this just a side effect of the complexity/power of uCommerce?

3) How can I get the shipping address from any page outside of the checkout pipeline?

Thanks for your time, 

Zac