WPF

<allow-from http-request-headers="*">

arkiboys wrote:

would like to have one main page

<Navigation:Frame x:Name="MainContent"  Grid.Column="1" HorizontalContentAlignment="Stretch"  VerticalContentAlignment="Stretch"   
                         Source="Home" UriMapper="{StaticResource MyMapper}">

private void btnNavigate_Click(object sender, RoutedEventArgs e)
        {
            mainFrame.Navigate(new Uri("/Page1.xaml", UriKind.Relative));
        }

public static class MainUI
{

    public static void NavigateTo(string sViewName)
    {
        //Get the content frame from the main page via the application
        Frame oFR = (Application.Current.RootVisual as FrameworkElement).FindName("MainContent") as Frame;
        NavigateTo(oFR,sViewName);
    }

    public static void NavigateTo(Frame oFR, string sViewName)
    {
        oFR.Navigate(new Uri(sViewName, UriKind.Relative));
    }

private void ControlNavigate(object sender, RoutedEventArgs e)
    {
        Frame oFrame = this.FilterContent;//this is a frame on a non main page view
        string sURL = "Blank";
        switch ((sender as HyperlinkButton).Content.ToString())
        {
            case "Accounts":
                sURL = "AccountFilter";
                break;
            case "Elements":
                sURL = "ElementNodeFilter";
                break;
            case "Products":
                sURL = "ProductFilter";
                    break;
        }
        gUI.NavigateTo(oFrame, sURL);

    }

<br />
Since in the Internet scenario the client's message is transferred to the service over plain HTTP, it is vital to protect its content (both the client's credentials and the body of the message) by encrypting it. Encryption will provide for message integrity and privacy...<br />
Once the message is decrypted, WCF will read the client's credentials from the message, authenticate the client, and allow it to access the service. The real picture is a bit more complex, because WCF also needs to secure the reply messages and callbacks from the service to the client. One of the standards WCF supports deals with setting up such a secure conversation. In fact, several calls are made before the first request message from the client to the service, where WCF on the client's side generates a temporary shared secret it passes encrypted (using the service certificate) to the service. The client and the service will use that shared secret to protect all subsequent communication between them.<br />

Kevin Marois wrote:

the content comes out as text

<ItemsControl Grid.Row="1" ItemsSource="{Binding ShipList}" HorizontalAlignment="Center">
    <ItemsControl.ItemsPanel>
        <ItemsPanelTemplate>
            <toolkit:WrapPanel/>
        </ItemsPanelTemplate>
    </ItemsControl.ItemsPanel>
    <ItemsControl.ItemTemplate>
        <DataTemplate>
            <HyperlinkButton Click="HyperlinkButton_Click" Tag="{Binding Path=ShipID}" HorizontalContentAlignment="Center" >
                <Grid HorizontalAlignment="Center" >
                    <Grid.RowDefinitions>
                        <RowDefinition/>
                        <RowDefinition/>
                    </Grid.RowDefinitions>
                    <Image Grid.Row="0" Stretch="None" Source="{Binding Path=ShipLogoUri}" />
                    <TextBlock Grid.Row="1" Foreground="Blue" Text="{Binding Path=Ship}" HorizontalAlignment="Center" />
                </Grid>
            </HyperlinkButton>
        </DataTemplate>
    </ItemsControl.ItemTemplate>
</ItemsControl>