I have been meaning to mention how cool and informative the info is in the WSE3 trace files. Not only does it show you the soap, but leaves a step by step trail of processing. Here is a sample file from a simple HelloWorld request being made from a client using a UsernameoverX09 policy asserstion.

<?xml version="1.0" encoding="utf-8"?>
<log>
  <outputMessage utc="9/23/2005 7:04:53 PM">
    <processingStep description="Unprocessed message">
      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
        <soap:Body>
          <HelloWorld xmlns="http://tempuri.org/" />
        </soap:Body>
      </soap:Envelope>
    </processingStep>
    <processingStep description="Entering soap filter Microsoft.Web.Services3.Design.UsernameOverCertificateAssertion+ClientOutputFilter" />
    <processingStep description="Exited soap filter Microsoft.Web.Services3.Design.UsernameOverCertificateAssertion+ClientOutputFilter" />
    <processingStep description="Processed message">
      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
        <soap:Header>
          <wsa:Action wsu:Id="Id-3055d475-5038-45ae-9909-d7feb1241b7b">http://tempuri.org/HelloWorld</wsa:Action>
          <wsa:MessageID wsu:Id="Id-bc312d98-8815-4c65-a015-2cf87409140c">uuid:80c57c6f-7226-49a6-95ba-51c160841d30</wsa:MessageID>
          <wsa:ReplyTo wsu:Id="Id-d3c52946-1153-4ef6-85df-4e80506bb0a2">
            <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
          </wsa:ReplyTo>
          <wsa:To wsu:Id="Id-047058e6-d0e9-4592-8d10-2df4cd13d976">http://localhost:1624/WSE3_Demo2_Service/Service.asmx</wsa:To>
          <wsse:Security soap:mustUnderstand="1">
            <wsu:Timestamp wsu:Id="Timestamp-71acb0d5-9d5c-4d6d-beba-585045011528">
              <wsu:Created>2005-09-23T19:04:53Z</wsu:Created>
              <wsu:Expires>2005-09-23T19:09:53Z</wsu:Expires>
            </wsu:Timestamp>
            <xenc:EncryptedKey Id="SecurityToken-2eb49508-1d19-4dc8-ac98-df6037e4dce3" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
              <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5" />
              <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
                <wsse:SecurityTokenReference>
                  <wsse:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/2004/xx/oasis-2004xx-wss-x509-token-profile-1.1#X509ThumbprintSHA1" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">h9ksyrcUww2w4LrmubC2W11t988=</wsse:KeyIdentifier>
                </wsse:SecurityTokenReference>
              </KeyInfo>
              <xenc:CipherData>
                <xenc:CipherValue>(this goes on for a while...) Udj=</xenc:CipherValue>
              </xenc:CipherData>
            </xenc:EncryptedKey>
            <wssc:DerivedKeyToken wsu:Id="SecurityToken-a4ae21b8-bdab-4011-a7b2-c5e8f65bae44" Algorithm="http://schemas.xmlsoap.org/ws/2005/02/sc/dk/p_sha1" xmlns:wssc="http://schemas.xmlsoap.org/ws/2005/02/sc">
              <wsse:SecurityTokenReference>
                <wsse:Reference URI="#SecurityToken-2eb49508-1d19-4dc8-ac98-df6037e4dce3" ValueType="http://docs.oasis-open.org/wss/2005/xx/oasis-2005xx-wss-soap-message-security-1.1#EncryptedKey" />
              </wsse:SecurityTokenReference>
              <wssc:Generation>0</wssc:Generation>
              <wssc:Length>16</wssc:Length>
              <wssc:Label>WS-SecureConversationWS-SecureConversation</wssc:Label>
              <wssc:Nonce>0waVpgMtJcwLe6nu2EJfWA==</wssc:Nonce>
            </wssc:DerivedKeyToken>
            <xenc:ReferenceList xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
              <xenc:DataReference URI="#EncryptedData-95a05b43-87ff-4265-8220-0b0301998d5c" />
            </xenc:ReferenceList>
            <xenc:ReferenceList xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
              <xenc:DataReference URI="#EncryptedData-474cdefc-1a57-4848-9d3b-195021ac5f88" />
            </xenc:ReferenceList>
            <xenc:EncryptedData Id="EncryptedData-474cdefc-1a57-4848-9d3b-195021ac5f88" Type="http://www.w3.org/2001/04/xmlenc#Element" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
              <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc" />
              <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
                <wsse:SecurityTokenReference>
                  <wsse:Reference URI="#SecurityToken-a4ae21b8-bdab-4011-a7b2-c5e8f65bae44" ValueType="http://schemas.xmlsoap.org/ws/2005/02/sc/dk" />
                </wsse:SecurityTokenReference>
              </KeyInfo>
              <xenc:CipherData>
                <xenc:CipherValue> (this goes on for a while...) =</xenc:CipherValue>
              </xenc:CipherData>
            </xenc:EncryptedData>
            <wssc:DerivedKeyToken wsu:Id="SecurityToken-ef9f2efd-b777-4288-9a93-f7b24b9eb083" Algorithm="http://schemas.xmlsoap.org/ws/2005/02/sc/dk/p_sha1" xmlns:wssc="http://schemas.xmlsoap.org/ws/2005/02/sc">
              <wsse:SecurityTokenReference>
                <wsse:Reference URI="#SecurityToken-2eb49508-1d19-4dc8-ac98-df6037e4dce3" ValueType="http://docs.oasis-open.org/wss/2005/xx/oasis-2005xx-wss-soap-message-security-1.1#EncryptedKey" />
              </wsse:SecurityTokenReference>
              <wssc:Generation>0</wssc:Generation>
              <wssc:Length>16</wssc:Length>
              <wssc:Label>WS-SecureConversationWS-SecureConversation</wssc:Label>
              <wssc:Nonce>+G94xbAd/DYLEKwIvHIdTA==</wssc:Nonce>
            </wssc:DerivedKeyToken>
            <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
              <SignedInfo>
                <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" />
                <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1" />
                <Reference URI="#SecurityToken-6d4fff15-de0b-449d-ab5e-47ac5f5b4592">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>XOXZQd6B320w7VI/HbimntQgLI0=</DigestValue>
                </Reference>
                <Reference URI="#Id-3055d475-5038-45ae-9909-d7feb1241b7b">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>1kE5FH5eNF4vkBKNE9o0/vCJvks=</DigestValue>
                </Reference>
                <Reference URI="#Id-bc312d98-8815-4c65-a015-2cf87409140c">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>t/FJbUnIn0gLqoLt6eMRTFOTI/Q=</DigestValue>
                </Reference>
                <Reference URI="#Id-d3c52946-1153-4ef6-85df-4e80506bb0a2">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>9QxbDw3l7++M8PbJMur9JxcPf4c=</DigestValue>
                </Reference>
                <Reference URI="#Id-047058e6-d0e9-4592-8d10-2df4cd13d976">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>9l1Au73puBn71S7N/1XIBe2vRSY=</DigestValue>
                </Reference>
                <Reference URI="#Timestamp-71acb0d5-9d5c-4d6d-beba-585045011528">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>Ys2mZfoq7z+Ix/XyIYWTIDUvm28=</DigestValue>
                </Reference>
                <Reference URI="#Id-8d5987f2-3dd0-41aa-8dc5-5551bc171011">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>PkZhQS+mXa/s8BC0x09fp7BOeB8=</DigestValue>
                </Reference>
              </SignedInfo>
              <SignatureValue>tJZfFrgNccXPYc91i41uHxdrzXk=</SignatureValue>
              <KeyInfo>
                <wsse:SecurityTokenReference>
                  <wsse:Reference URI="#SecurityToken-ef9f2efd-b777-4288-9a93-f7b24b9eb083" ValueType="http://schemas.xmlsoap.org/ws/2005/02/sc/dk" />
                </wsse:SecurityTokenReference>
              </KeyInfo>
            </Signature>
          </wsse:Security>
        </soap:Header>
        <soap:Body wsu:Id="Id-8d5987f2-3dd0-41aa-8dc5-5551bc171011">
          <xenc:EncryptedData Id="EncryptedData-95a05b43-87ff-4265-8220-0b0301998d5c" Type="http://www.w3.org/2001/04/xmlenc#Content" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
            <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc" />
            <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
              <wsse:SecurityTokenReference>
                <wsse:Reference URI="#SecurityToken-a4ae21b8-bdab-4011-a7b2-c5e8f65bae44" ValueType="http://schemas.xmlsoap.org/ws/2005/02/sc/dk" />
              </wsse:SecurityTokenReference>
            </KeyInfo>
            <xenc:CipherData>
              <xenc:CipherValue>(this goes on for a while...) ==</xenc:CipherValue>
            </xenc:CipherData>
          </xenc:EncryptedData>
        </soap:Body>
      </soap:Envelope>
    </processingStep>
  </outputMessage>
</log>

October 17th

Tim will be doing a fantastic talk that I saw him do at TechEd 2005:

Top Ten Hands-On Tips and Tricks for Implementing ASP.NET Web Services

more info at www.vtdotnet.org

I'm so happy to already have two INETA gigs lined up.

I'll be speaking at WeProgram.net in Virginia Beach on December 6th.

Next will be Tech Valley.NET, in Albany NY on January 25th. I'll hope for now blizzards!

In addition to that, I will be speaking next month at the new group in Syracuse, NY  - CNY .NET Developer Group. Although they are now an INETA group, I am going there on my own because I grew up in the area and my parents still live about an hour away. I was really exicted when I heard that Andy was starting up this group so am very happy to be going there. So are my parents since I'll get to go see them, too!

I was astonished at how many people attended the Atlas talks. Here is a photo I took of the sea of people (I had to stand on a chair) during the first of the two sessions. I took this to show to my fellow ASPInsiders, but of course want to share with everyone. Click on the photo for a larger view.

I have worked in silence for a long time. When I drive in my car, I love talk radio. Of course, I can't listen to that when I'm coding. But I can't listen to music either - the words are distracting. I finally had a great idea today. I LOVE cuban music. I don't understand any form of spanish. So I can listen to it while I'm working without the words getting in the way. So I have been on www.batanga.com - Cubanismo music on and off all day. I think I could work all night!

John Mueller demonstrates a nifty debugger visualizer in his article on DevSource: Write Your Own Visualizer for VS Debugging. I have played with visualizers a lot, but have focused on data - like database data. John expands my world with his DateTime visualizer. Definitely check out his article.

Rather than focusing on my talks and demos for Code Camp IV: Developer's Gone Wild, I find I am spending all of my time getting decks and demos from various machines and vpcs all onto one computer. I am really happy that now I will have one computer to use for all of my demos - until it's time to start showing Vista (when I can get the video drivers to work with a projector that is).

I still haven't figured out how I managed to have four sessions at Code Camp.

Well, soon I'll have everything in one place and can get to the real task at hand...

I'll be the guy carrying the Accoridan case

not quite what Microsoft has in mind when they say "mobile pc" - but it works for me (so long as I don't have to carry it for him!)

I am terrified of flying and I do waaaay too much of it

http://www.cnn.com/2005/US/09/22/airliner.emergency.ap/index.html

but now walking is scary

http://www.cnn.com/2005/US/09/22/pedestrians.struck.ap/index.html

National Gardening Association

Burton Snowboards

Burlington location

Infrastructure Manager

IS User Support Analyst

Proejct Manager - Web

Bluehouse Group in Richmond, Vermont

We're looking for an experienced Web professional to join our team. Someone who can design and construct Web pages, both visually and functionally. Someone who is as comfortable in front of the client as in front of the computer. Solid understanding of designing for the Web, and expertise with XHTML, CSS, JavaScript required. Flash, PHP, MySQL a plus. Project management skills also helpful. Adobe Creative Suite expertise desired. Salary commensurate with experience. Benefits package including retirement plan and health insurance. hr@bluehousegroup.com
 

Jobs in the Burlington VT location

Propeller Media Works

More details on their website: www.propelled.com

PHP/Web Developer

Propeller Media Works seeks candidates eager to join its experienced team of web designers and programmers. This is not a design position. Instead we seek a programmer with an eye for design to assist primarily in the development and ongoing integration of our proprietary PHP/MySQL based CMS and e-comm systems, B-B and B-C e-comm system integration, and custom web application development.

Jr. Developer

Propeller Media Works seeks exceptional candidates eager to join its experienced team of web designers and programmers. This is not a designer position, but the ideal candidate will have respect for design and at least 2 years of paid work experience producing websites. Must be solid in Fireworks, Dreamweaver, Flash, CSS, and have a strong understanding of the open source toolsets (PHP/MySQL). Bonus for SEO/SEM and Mac/PC hardware/software/network skillsets.

Opportunities Credit Uniont, Burlington Vermont

http://www.oppsvt.org/jobs.htm

Adam Cogan is doing workshops in 4 US cities about moving access apps to .NET.

Here's more info and the US and other worldwide schedule

The U.S. workshops are soon!

• L.A. - (today) 9/22 - 23
• Seattle - 10/3 - 4
• Dallas 10/6 -7
• NYC 10/10 - 11

Sam's post reminded me that I meant to mention my big problem when I tried to show Vista and Glass to Vermont.NET on Monday night. It wouldn't work with the projector. In fact, when I plugged the projector into my laptop, the resolution changed on the laptop and did not revert when I yanked the plug out. Luckily it was a smallish group and I finally gave up and said "gather round" and showed them some of the pretty features.

All of the rest I did on my XP box with a Virtual PC since I had way too many versions of VS2005 required to show Atlas demos and LINQ demos.

Whoa - Robert Scoble said he was on the home page of Microsoft.com, so I had to go see. When I went to the home page I noticed this item:

News: Microsoft realigns for next wave of innovation and growth

I followed the link and among the subtitles see all kinds of interesting news! Better go look for yourself!!

There is no question in my mind that LINQ is going to be very important to .NET developers.

Larry groks the plumbing much better than I do at this point. I'm focused on what it will let me do.