Boss sent me to DevConnecitons again and it was great!

Here are my notes for the SharePoint classes I sat in on.

• Pre Conference Work shop: SharePoint Workflows HPR201 by Rober Bogue.
  • SharePoint Designer workflows pros/cons:
    • Not truely "portable" becuase of list GUID's in XAML and must be associated with an item.
    • No code needed.
    • GUI based.
      
  • Visual Studio workflows pros/cons:
    • Complete control.
    • Require strong development skills.
    • Requires more time to develop.
  • SharePoint Designer Workflows can be extened with Visual Studio.
  • Required for Visual Studio Dev:
    • Visual Studio Extensions for Workflow Foundation.
    • VSeWSS
  • Workflow Types:
    • Sequential (think SharePoint Designer workflows)
    • State Machine.
  • Can run a WorkFlow on a content type.
  • Note: Pauses in SP Designer WorkFlows are averaged out to ~5 minutes due to the SP timer trigger interval.
  • WorkFlow DLL must be deployed to the GAC.
  • When building a VSworkflow, it becomes a workflow type availible in the List settings -> Workflow.  YEA!
  • Set a fault handler to catch all faults in your VS Workflow type (see Robert Bogue's Blog).
  • Tip: Restart WSS timer every 4 hours due to memory leaks.
  • Errors are logged here = 12\logs\.
    
  • Get log viewer utiltiy from CodePlex here.
  • .wsp files is a special cab file.
  • Brackets for GUID's are allowed and only allowed in the ContentType.xml.  It is the only place in sharepoint.
  • DisplaceOnUpgrage="TRUE" required inContentTypes.xml.  This is becuase any new changes will not upgrade by default.
  • Included in this zip is a nice LDAP class.  200804SPConn-Workflow.zip (4.28 mb)
  • Here is a nice web debugging utitlity (HTTP debugger proxy): http://www.fiddlertool.com/fiddler/
• More to come soon.
  

If you are trying to consume a Sharepoint web service - from a Windows Application - on a server that is configured for both SSL and Require Client Certificate, you need to do the following:

1. First, export the client certifiate to a file following the directions in the section titled: "Step 1: Export the Client Certificate to a File" at this link: http://msdn2.microsoft.com/en-us/library/aa302408.aspx.
2. Next you need to tell the web service to use that certificate like this: lists.ClientCertificates.Add(X509Certificate.CreateFromCertFile("C:\file_where_certificate_is_stored_from_above_step");
3. Finally (and this is the part that Microsoft left out of their instructions) you need to authenticate to the web service using ONE of the following methods:
   • lists.Credentials = CredentialCache.DefaultNetworkCredentials; <-- This uses the credentials of the logged on user.
   • CredentialCache cache = new System.Net.CredentialCache(); cache.Add(new Uri(lists.Url), "Basic", new NetworkCredential(UserID, Password, Domain)); lists.Credentials = cache;