• Your keyboard currently defaults to French when you reboot, and
• Your password will only work on the correct URL location

is really always a good idea. Eh? Also, saying "Right?" when hitting Enter may actually be the way out of the conundrum, eh, Meg? (http://twitiq.com/Origameg) (Or at least it's a new game?)

In any case, I did manage to show the basic functionality after a fashion -- thanks to Yavor reminding me of the correct URL. Sigh. Well, the next morning we made it all work. However... because I was busy making Win8 work on that slate with buggy video drivers, I did not know what the heck was going on **prior** to the demo work. I've just come up for air from that conference, and discovered what that song-ee thing was prior to the announcement and oh, boy. I just do not know what to say. Actually, I do. But my daughter -- my daughter -- can read this blog, and I think I'll do better speaking with her directly.

But... just... no. That not only isn't about development, but it's wrong, wrong, wrong. I'm not speaking as an employee, just as a human. Please, marketing people, let's learn from this, OK?

Now then: Since Meg tweeted this, too: No, I didn't cancel the Friday afternoon session because of "Right" -- I thought it MUST have been funny to others, and we broke in with the correct URL and you all applauded as you should have -- no, I had a better excuse. There's someone special in my life, and I needed to be with that person. So I went. And it's all good. Plus --> I DID do the What's New session in the morning at 9 AM (I know you weren't there because it was entirely a male audience) and things went fine THEN. Of course, I remembered the URL. :-)

And NDC is a great conference. I hope to come back next year. Meg --> you want me to do the high-perf messaging as a webinar? Either that, or invite me, and I'll come do it for you and your colleagues.

Cheers, me.

If I'm creating a set of applications, and all I need is access control to that application, I'll need to use an ACS namespace to configure that application as a relying party (which I would call a relying or dependent application, but I don't write the names). But do I use an ACS namespace that is already in use? Do I create a new ACS namespace just for that application? Or are there categories of people or clients that I can group into an ACS namespace, trusted by one or more applications LIKE those used by those people or clients?

I'm curious what you do, but I'm doing more work figuring out the best way to go here from the perspective of the real world. More soon.

We're soon going to release some guidance around building multi tenant applications in Windows Azure, and this integration pack is very, very important for that design approach as well. Have a look. 

Scott has tons of experience to help you understand Azure, its services, and get you started building applications over two days -- few could be better to learn from. I am really looking forward to it. If you're in the area and interested, please come.

Warning: Fault named ApiException in operation copyCampaigns cannot be imported.
 Unsupported WSDL, the fault message part must reference an element. This fault
message does not reference an element. If you have edit access to the WSDL docum
ent, you can fix the problem by referencing a schema element using the 'element'
 attribute.

In any case, the difference between ASR and Svcutil.exe is that one has the UseSerializerForFaults option easily available to you as a switch on the command line. Using this switch instructs Svcutil.exe to use the XmlSerializer to handle faults instead of the default, which is the DataContractSerializer. In this case, although Svcutil.exe has indicated that the WSDL for the fault is flawed, it continues to import the service operation. If you want to enable VS ASR to do the same thing:

1. Click Show All Files in the Solution Explorer.
2. Open the Reference.svcmap file in your service reference.
3. Set the option <UseSerializerForFaults> to false in Reference.svcmap and save it. (NOTE: Take care NOT to update the service reference, as doing so resets the option to true.)
4. Open the reference.cs and you should see the operations generated.

 The WSDL for the fault contract will still need to be modified before the tools can generate the fault contract propery, but at least you can get your service proxies generated. Hope this helps. It's part of a larger series of issues revolving around this area. For one view, see http://dotnetbutchering.blogspot.com/2010/03/add-service-reference-duplicates.html, which points out a bug that **may** have been fixed in a more recent version of the .NET Framework -- or may not. I'll try to find out tomorrow.

private void LoadSupportSolutionsSection(ItemCollection itemCollection, XElement category)
{
    // Solution, url att, Title, Description.
    var solutions = from sol in category.Elements("Solution")
      select new TreeViewItem {
        Header = sol.Element("Title").Value, 
        Tag = sol.Attribute("url").Value,
        ToolTip = new ToolTip()
        {
          Content=sol.Element("Description").Value,
          StaysOpen=true
        }
      };

    foreach (TreeViewItem item in solutions)
    {
        itemCollection.Add(item);
    }
}

A very simple linq query spun from from XML returned from a Web service. The TreeViewItem is a WPF tree view item. So how do I write the select portion such that it inserts into the TreeView.Items collection each newly created TreeViewItem?

Anyone have an idea? I have two or three creative ones, but I have tried them out yet. Any suggestions appreciated....

ASIDE: Some people have noticed that the WCF implementation on the phone does not support "easy" Basic authentication of HTTP. No, it doesn't. But that's by design to protect you from "accidentally" using passwords in the clear over the network. Perhaps that's too much "protecting you", but it is documented here, in the note in the topic. If you don't use HTTPS -- that is, if you use HTTP -- the Client.Credentials property is ignored by design.

SECURITY NOTE: Because whenever sample code does not mention this, there's always some people in a big hurry that you have to remind: Obtain the username/password in a secure fashion. The most reasonably secure fashion is to prompt for it so that the user can enter it in a PasswordBox. However, there are other ways to encrypt in a strong way the strorage of such data on the phone. More in the future about several ways, but one is described here by Rob Tiffany: Don’t forget to Encrypt your Windows Phone 7 Data.

Using the WebClient Class (a good example with slightly different style found here!)

Using System.Net;

WebClient client = new WebClient();

// Handle the response when it comes.
client.DownloadStringCompleted += new DownloadStringCompletedEventHandler(client_DownloadStringCompleted);

// Your password; some services will call this a key, or a secret, or something.
string accountkeyOrPassword = "<account or key or password goes here>";

// Add the username/accountkeyOrPassword to the Client.Credentials property by creating a new NetworkCredential
client.Credentials = new NetworkCredential("accountKey", accountkeyOrPassword);

// Handle the response
client.DownloadStringAsync(new Uri("https://api.datamarket.azure.com/Data.ashx/data.gov/Crimes/CityCrime?$filter=City%20eq%20%27Seattle%27&$top=100"));

Using the HttpWebRequest Class

HttpWebRequest client
    = WebRequest.CreateHttp(
 new Uri("https://api.datamarket.azure.com/Data.ashx/data.gov/Crimes/CityCrime?$filter=City%20eq%20%27Seattle%27&$top=100")
    ) as HttpWebRequest;

// Your password; some services will call this a key, or a secret, or something.
string accountkeyOrPassword = "<account or key or password goes here>";

// Add the username/accountkeyOrPassword to the Client.Credentials property by creating a new NetworkCredential
client.Credentials = new NetworkCredential("accountKey", accountkeyOrPassword);

// To support Windows Azure DataMarket
client.AllowReadStreamBuffering = true;

// Call and handle the response.
client.BeginGetResponse(
    (asResult) =>
    {
        Dispatcher.BeginInvoke(
            () =>
            {
                try
                {
                    var response = client.EndGetResponse(asResult);
                    System.IO.StreamReader reader = new System.IO.StreamReader(response.GetResponseStream());
                    responseString = reader.ReadToEnd();
                }
                catch (WebException failure)
                {
                    throw failure;
            }
        });
     },
     null
);

In a next post, I'll show how to use several different optimized client libraries to do this work.