George Durzi

MobileMe: Internet Explorer 7 is not fully supported

gdurzi — Sun, 20 Jul 2008 00:51:17 GMT

As of this past Friday, the line to buy an iPhone 3G at Apple's Michigan Ave. store in Chicago was still almost a block long - apparently, the same scene is repeating itself across the country. For the most part, this isn't because of low inventory, but because of the ridiculous in-store activation process every customer has to go through.

A group of us on the way to lunch were joking about the iPhone 3G's (I refuse to refer to it as just "iPhone", it's the iPhone) successful but frustrating launch, when the conversation turned to Apple's new service MobileMe.

It's amusing how people are so willing to forgive Apple when they fumble something. MobileMe wasn't even working for a few days after its launch. Even funnier, Apple had to clarify what what they really meant by "push", and that some of MobileMe's services didn't actually use "push" technology.

Someone then mentioned that if you browsed MobileMe in IE7, you would get warned that you wouldn't enjoy the full experience because of IE7's compatibility issues with web standards.

I had to see this for myself ...

Let me say this up front, I am not an Apple basher ... As a matter of fact, I am writing this on a Macbook Pro, my wife and I stood in line and bought our iPhone 3Gs last weekend, and our place is littered with various generation iPods.

Maybe Apple is making a statement; that they're sick of having to program around IE's non-compliance with web standards? I commend that - I'm having to deal with some cross-browser JavaScript issues on a project, and let me tell you, it ain't fun.

Did Apple somehow forget though that the overwhelming majority of iPod and iPhone users will connect them to XP and Vista machines running IE6 or IE7?

Do they think that Joe-web-surfer understands the first thing about web standards compliance?

I guess somebody eventually has to draw a line in the sand when it comes to this. Just found it funny that Apple would call out IE7 like this, when as of June 2008 IE7 and IE6 combined still account for over 50% of the browser market share.

Getting called out for using IE7 is bad enough, I wouldn't want to see what MobileMe says if you browse it using IE6 :)

OCSDKWrapper Project on CodePlex

gdurzi — Sat, 05 Jul 2008 22:40:46 GMT

A colleague of mine - Peter Walke - was working on an internal project where he needed to quickly integrate some functionality provided by the Office Communicator SDK. Having worked on several projects involving Communicator automation, he asked me if I could give him some code he could simply drop into his project.

The Office Communicator SDK is generally easy to use, however, the code to connect to communicator, monitor the status of the connection, and clean up if the connection is lost can be complicated. I quickly realized that it's very inefficient and inelegant to have to paste this large blob of code into every project that used the Office Communicator SDK.

I decided to wrap that functionality into a helpful class library, where the developer's only responsibility would be to create an instance of the class - letting it handle all the underlying plumbing with Communicator.

While I was at it, I also baked in a number of helpful utility functions into the wrapper. This includes functions to trigger various types of Communicator conversations, perform Contact maintenance, query presence, and several others.

I create and published the OCSDKWrapper project, along with a sample application built using it, into CodePlex. You can find the project at http://www.codeplex.com/OCSDKWrapper.

Design Decisions

I worked on this over a couple of days this weekend, and made a couple of design decisions to finish the project quickly and get it published:

You still have to reference CommunicatorAPI in your application.
- I didn't see any real worth in creating DTO classes for every class in the Office Communicator SDK.
I left all the Communicator event parameter variable names as-is, even though I wasn't fond of the naming scheme

CodePlex

I've never created a project on CodePlex before, who knew picking what type of license to use would be so complicated.

If you're interested in contributing to the project, have some feedback, or want to report a bug, please contact me via this blog or by posting on the project page on CodePlex.

Sample Application

In the project's source code, you will find a simple sample application that was built using the OCSDKWrapper. The application displays the current connection status, the signed in user's status, and a running list of events that were raised by Office Communicator.

Take a look at the source code in the sample application, you'll see how quickly you can get up and running.

To do

Documentation
Unit tests

WPF/XBAP IOException: Cannot locate resource app.xaml

gdurzi — Tue, 24 Jun 2008 14:32:24 GMT

I'm working on an XBAP project where deploying it involves publishing it as a ClickOnce manifest using Visual Studio 2008's publishing features. I'm working with the RTM version Visual Studio 2008 Professional Edition.

Occasionally, the publishing process would fail for no good reason even though the project compiled successfully. When the publishing process eventually succeeded, I would get the following error when running the application:

IOException: Cannot locate resource app.xaml

After that happened, I wouldn't even be able to run the project in Debug mode from Visual Studio - I would get the same error.

In order to get the project to run again, I would have to open app.xaml, edit it, undo the edit, and save it. Blew my mind.

An extensive Google search showed that most people reported this issue when using the Beta 2 build of Orcas. I can report that this issue still occurs in the RTM version.

I finally figured this out, and am now able to publish my project consistently without ever seeing this error. Here's what my publishing process looks like now:

If your project is under source control, your .csproj or .vbproj needs to be checked out
You need to delete previously published files
- Delete the contents of publish\
- Delete the contents of bin\Debug\app.publish
- EDIT: I also noticed that I need to have the "Automatically increment revision with each publish" checkbox on the Publish tab of the project properties checked.

I hope this saves you some frustration.

TechEd 2008 Happenings

gdurzi — Tue, 03 Jun 2008 03:46:11 GMT

Technorati Tags: TechEd

I'm going to be at the TechEd bloggers lounge on Wednesday, June 4th from 3 to 4pm to discuss and answer questions about the Unified Communications works Clarity did for the conference.

Here's some of the stuff we'll be showing throughout the week:

Office Communicator Presence Controls for WPF
Office Communicator Vista Gadget
TFS Spy - Visual Studio Add In

It's pretty exciting to be here! I'll be in the Unified Communications area of the Technical Learning Center most of Tuesday and Wednesday.

If you miss any of our demos in the sessions, drop by for a impromptu demo!

LiveMeeting Recording from geekSpeak UC show

gdurzi — Thu, 22 May 2008 19:38:52 GMT

If you're interested, the folks from geekSpeak have made available a recording of yesterday's show - Contextual Collaboration using Unified Communications.

Thanks to the geekSpeak hosts, Glen Gordon and Mithun Dhar. I really enjoyed being on the show and am a big fan of the format.

MSDN geekSpeak show on 5/21 at 2pm CST

gdurzi — Mon, 19 May 2008 15:16:39 GMT

I'm going to be a guest on MSDN geekSpeak this coming Wednesday at 2pm CST, the topic is Contextual Collaboration Using Unified Communications.

We're going to discuss how to communications-enable an application by going through a couple of demos that we built for this year's UC track at TechEd in Orlando:

Office Communicator Vista Sidebar Gadget
WPF Presence Controls for Office Communicator (used in the gadget demo)

Both projects are intended to be samples and will be made publicly available (including source code) after TechEd 2008.

I'll be going through the source code and digging into how to use the Office Communicator SDK in a project.

geekSpeak format

The geekSpeak format is pretty cool; there are no slides, just questions from the audience which end up driving the direction of the session.

I'm involved in some user group events, and getting the audience to interact can be like pulling teeth! Maybe the fact that the audience submits their questions via LiveMeeting has something to do with it ...

Regardless, it's refreshing to participate in a user-driven session instead of talking at your audience from a pptx deck!

Office Communicator Vista Sidebar Gadget

The gadget I'll be showing was built in WPF and provides functionality such as:

Creating list of Favorite 5 contacts
Dynamically calculating who your Top 5 contacts are
Retrieving voicemail from Exchange

Here's a screenshot of the gadget docked in the sidebar:

If you can't make the live broadcast time for the show, all the shows are archived for later viewing. I'm looking forward to hijacking a conference room here and and hanging an "on the air" sign at the door :)

TECH Cocktail Conference - May 29th in Chicago

gdurzi — Sat, 03 May 2008 22:47:31 GMT

When I first heard about TECH Cocktail, I was surprised to see that such an organization even existed in Chicago - I didn't realize that there was such a vibrant technology community here!

TECH Cocktail has done a bunch of mixers in Chicago and has recently expanded to other cities. They're putting on the inaugural TECH Cocktail Conference on May 29th here in Chicago.

There's a nice lineup of speakers, and Jason Fried from 37 Signals is giving the keynote. I'm looking forward to that one, I'm a big fan of what 37 Signals is doing and really enjoyed reading about their take on software development in Getting Real.

Contact Name Resolution using the Office Communicator SDK

gdurzi — Tue, 29 Apr 2008 13:38:58 GMT

In my continuing efforts to bring you useful nuggets from the Office Communicator SDK, I bring you IMessengerContactResolution.

I realized that I needed something like this when I wasn't able to resolve contacts given their SMTP address by using the IMessenger::GetContact method. The IMessenger::FindContact methods wasn't helpful because it actually invoked the Communicator's UI to find a contact.

I came across IMessengerContactResolution::ResolveName in the SDK, but saw that the ResolveName method was marked as Not Implemented. Well, it is ... I didn't find out until someone on the UC team sent me a code snippet that used it. Moral of the story: give it a shot even if the SDK says it's not implemented.

Scenario

The scenario I was working with is that a user could drag a contact out of Communicator into my application. What you get in the drag arguments happens to be the contact's primary SMTP address, which may or may not match their Sip Uri, e.g. john.doe@contoso.com vs. jdoe@contoso.com. A lot of organizations do this, and there's really no standard way to "discover" a user's Sip given their SMTP and vice versa.

My ResolveContact method tries to resolve its input string a couple of different ways. As usual, when programming against the Office Communicator SDK, you unfortunately have to control logic flow using try/catch statements. I feel dirty every time I do that, but hey, my hands are tied :)

ResolveContact

In my application, I carry around a class-level variable called _resolver to perform contact resolution:

private IMessengerContactResolution _resolver;

When I handle the Communicator sign-in event, I set up _resolver by casting my main communicator object to IMessengerContactResolution:

_resolver = _communicator as IMessengerContactResolution;

This is pretty common when writing applications that use the Office Communicator SDK, you of course are responsible for cleaning up those objects which I do when I handle the Communicator sign-out event.

Here's the code for my ResolveContact method:

void ResolveContact(string dropString, out string sipUri, out string displayName)
        {
            try
            {
                sipUri = null;
                displayName = null;

                try
                {
                    // Scenario 1: User enters a Sip Uri
                    //  If so, GetContactDetails will return a display name
                    //
		    // Code for this method not included, 
		    //  It simply called IMessenger::GetContact
                    GetContactDetails(dropString, out displayName);
                }
                catch
                {
                    sipUri = null;
                }

                if (String.IsNullOrEmpty(displayName)) // Not a match based on Sip Uri
                {
                    try
                    {
                        // Scenario 2: User enters an SMTP address
                        //  Try to resolve the SMTP address into a Sip Uri
                        //
                        sipUri = _resolver.ResolveContact(ADDRESS_TYPE.ADDRESS_TYPE_SMTP,
                            CONTACT_RESOLUTION_TYPE.CONTACT_RESOLUTION_CACHED_ONLY, 
		            dropString);
                    }
                    catch
                    {
                        sipUri = null;
                    }

		    // Not a match based on SMTP Address
                    if (String.IsNullOrEmpty(sipUri))
                    {
                        try
                        {
                            // Scenario 3: User enters a contact's display name
                            //  Try to resolve the Display Name into a Sip Uri
                            //
                            sipUri = _resolver.ResolveContact(
				ADDRESS_TYPE.ADDRESS_TYPE_DISPLAY_NAME,
                                CONTACT_RESOLUTION_TYPE.CONTACT_RESOLUTION_CACHED_ONLY, 
				dropString);
                        }
                        catch
                        {
                            sipUri = null;
                        }
                    }

	            // Success - get the contact's Display Name
                    if (!String.IsNullOrEmpty(sipUri)) 
                    {
                        GetContactDetails(sipUri, out displayName);
                    }
                }
                else
                {
                    sipUri = dropString; // Scenario 1
                }
            }
            catch (Exception exception)
            {
                throw exception;
            }
        }

Ad-hoc phone number dialing using the Office Communicator SDK

gdurzi — Sat, 12 Apr 2008 02:51:51 GMT

I'm gonna chalk this up to one of things that's painfully obvious after the fact... I'm using the IMessengerAdvanced::StartConversation method of the Office Communicator automation SDK to dial ad-hoc phone numbers, e.g. simply dialing Clarity's front desk at +13128633100 as opposed to selecting a contact in Communicator and dialing one of its listed phone numbers.

Communicator would attempt to dial the number but the call to StartConversation would throw a not-so-helpful COMException.

vConversationData

The SDK documentation describes the StartConversation method, but is vague on its parameters. The trick here is to correctly populate the vConversationData parameter.

Here's what the SDK says about the vConversationData parameter:

A VARIANT value to hold a XML binary large object (BLOB) used to send data dependent on the chosen conversation type. For focus-based conference call, this parameter is used to pass in the conference URI as the content of a <ConfURI> element. For PSTN calls, the parameter contains an array of TEL URIs, as a <TelURIs> element.

Pretty misleading, because we won't be BLOB'ing anything!

Formatting Phone Numbers

Before being passed to the StartConversation method, phone numbers have to be prefixed with tel: to explicitly specify that this is a phone number.

As part of configuration Office Communications Server for voice, you can add regular expressions to normalize the way Communicator dials phone numbers, e.g. when I simply dial 39XX, Communicator knows that this is my Clarity extension and dials it as +131286339XX.

What this means is that if you have these rules in place, you don't need to worry much about normalizing the phone number before passing it to the StartConversation method.

Of course, if you specify a phone number that doesn't match any of your normalizing regular expressions, Communicator won't be able to make the phone call. Communicator handles this gracefully, you don't need to handle an exception in your code.

IMessengerAdvanced::StartConversation

Here's the obvious part:

The way the vConversation data document was phrased, I was trying stuff like:

XML Blob, I think not ...

Updated Tafiti SharePoint Search

gdurzi — Sat, 22 Mar 2008 23:13:00 GMT

If you haven't seen Tafiti Visual Search, wander on over to CodePlex and check it out. Kevin Marshall and I contributed to the project by extending Tafiti to search against SharePoint. The Windows Live team recently made significant updates to the Tafiti project, and we just checked in a change set with the updated SharePoint search code. You can download the change set and configure it to search against your SharePoint portal.

Automating Office Communicator 2007 using the Microsoft Office Communicator 2007 SDK

gdurzi — Sat, 22 Mar 2008 21:12:17 GMT

The Microsoft Office Communicator 2007 SDK allows you to automate a running instance of Office Communicator 2007 to integrate Communicator functionality into your applications.

There are a bunch of other SDKs that the Unified Communication team puts out. The difference between them can get confusing, let's clear some things up for this specific SDK.

You need to have Office Communicator 2007 installed and running
The SDK works by automating functions of Communicator, e.g. when you start an IM conversation through code, a Communicator window actually launches

Check out the "what others are downloading" section of the download link above for links to some of the other SDKs.

The SDK comes with a help collection, but no sample applications. There are some good snippets of code in there, but it's pretty dry reading.

I put together a sample WinForms application that showcases some of the functionality that the SDK provides, it beats reading the help file to figure out what the difference between the IMessenger, IMessenger2, and IMessenger3 interfaces is.

The Visual Studio 2008 project includes some presence controls which you can download separately if you'd like.

I've worked on a couple of projects that involved using this SDK, here are some useful tips from stuff I've come across:

Communicator allows you to add distribution lists as contacts, e.g. I add the Clarity "All Employees" group and automatically get everyone in Clarity on my buddy list. If you do this, you don't get the individual members of the group as contacts - they won't be in Messenger.MyContacts
Clean up after yourself. This a COM automation API, use Marshal.ReleaseComObject to properly dispose of Communicator objects
Various interfaces inherit from each other to provide more functionality, e.g. IMessenger3 inherits from IMessenger2 which inherits from IMessenger1

Download the source

Review: Google Calendar Sync

gdurzi — Thu, 13 Mar 2008 20:45:56 GMT

For a while now, I've been looking for a solution to sync my Google Calendar with Outlook. My wife and I have a Google Calendar on which we have "family events", she subscribes to it from iCal on her MacBook, and I subscribe to it from within Outlook and overlay it on top of my main calendar.

The only problem for me with this setup is that I don't get the items from the Google Calendar in my Outlook Calendar. I don't get reminders for them, and can't see them on my smart phone.

There's a few tools out there that do this, but after reading Jeff Atwood's post - A Question of Programming Ethics - about some unscrupulous applications, I'm hesitant to fork out my username and password to anybody.

Google recently released Google Calendar Sync to provide two-way or one-way sync between Outlook and Google Calendar and vice versa.

Configuration

Once installed, GCS puts an icon in your system tray which you can use to configure it.

One-way Sync from Google Calendar to Outlook

I was specifically interested in one-way sync from Google Calendar to Outlook, and set it to sync every 60 minutes (probably overkill).

The one-way sync works pretty well, but I found an annoying side-effect. Every time GSC performs a sync, I find a bunch of empty meeting requests in my Deleted Items folder in Outlook. They are all dated 12/31/1979 and are scheduled with random people from my company's Global Address Book.

Wonder what these are all for and why GSC is reaching into my Global Address Book ...

One-way Sync from Outlook to Google Calendar

Uneventful, same thing with the phantom meeting requests in the Deleted Items folder though. One of my colleagues mentioned that not all of his meeting requests in Outlook were being copied over to Google Calendar - I didn't verify this (too much crap in my Calendar to go through it one item at a time).

Two-way Sync

Nothing profound to add here.

Verdict

Google Calendar does a great job of inheriting the properties of Outlook meetings, e.g. the attendee list and each individual's status, your response to the meeting request, and the text of the meeting. It even puts a handy "maps" link to map whatever is in the Location field of the meeting request.

You might cause some confusion if you edit an Outlook meeting from Google Calendar, you probably should only edit meeting requests that originate in Outlook within Outlook itself.

Other than the strange issue with the meeting requests in the Deleted Items folder in Outlook, I have no complaints. I hope to see the issue resolved in future releases, I've come across some annoyed mentions of it on the web.

I would also like to see Google consolidate what it puts in the System Tray, there's no reason this can't be a part of the Gmail Notifier for example.

Update (03/31/2008)

I downloaded an update and it seems to have fixed the issue with the Calendar items in the Outlook Deleted Items folder.

pixel8

gdurzi — Wed, 05 Mar 2008 00:37:00 GMT

Craig Shoemaker, my good friend and former co-worker, recently joined Infragistics as a new media evangelist. Today, he launched a new video podcast series called pixel8 which is going to focus on the convergence of user experience development with traditional software development.

The days of graphic designers mocking up pretty stuff in PhotoShop and tossing it over the fence are numbered! New technologies such as WPF and Silverlight are forcing UX and traditional developers to work together more closely than ever.

Craig's already got a few great shows lined up with Scott Guthrie, Josh Smith, and other new media ninjas - be sure to check it out.

Extracting IM Conversation Text using the Office Communicator SDK

gdurzi — Mon, 18 Feb 2008 18:22:34 GMT

The Office Communicator 2007 SDK is one of a bunch of SDKs available for the Office Communications Server 2007 product suite. This particular one is used to automate a running instance of Communicator 2007. For example, you can interact with Communicator to start text, audio, or video conversations. You can also respond to certain Communicator events in code, such as the creation of a new conversation window.

If you've tried to extract the contents of an IM conversation window using IMessengerConversationWnd::History, you might have noticed that the History property always seems to return null.

The trick here is that the conversation text isn't injected into the IM window at the exact moment that it is created; you have to use a timer to check for when the History property returns something other than null.

Here's some code that shows how to use System.Threading.Timer to poll the conversation window. This code doesn't go into how to use the CommunicatorAPI COM objects to hook into Communicator from within your application and wire up the necessary events - the SDK I linked to above has plenty of examples on how to do that.

If you have any questions about that though, hit me up and I'll try to answer them.

We'll start by declaring a Timer object in our class, and also a plain object to hold a reference to a specific IM conversation window:

private Timer timer = null; 
private object convWindow;

Communicator WindowCreated Event Handler

In the Communicator WindowCreated event handler, we can tell whether this is an incoming or outgoing conversation window by comparing the window's HWND property to a local variable called windowHandle.

        void communicator_OnIMWindowCreated(object pIMWindow)
        {
            try
            {
                IMessengerConversationWndAdvanced imWindow = 
                    (IMessengerConversationWndAdvanced)pIMWindow;

                if (((IMessengerConversationWndAdvanced)pIMWindow).HWND == windowHandle)
                {
                    // outgoing
                }
                else
                {
                    // incoming
                    windowHandle = imWindow.HWND;
                    HandleIncomingMessage(pIMWindow);
                }
            }
        }

Setting up the Timer

For this example, I'll use a function called HandleIncomingMessage to handle an incoming conversation. I'll pass the conversation window as a parameter to the function.

        void HandleIncomingMessage(object pIMWindow)
        {
            IMessengerConversationWndAdvanced imWindow = 
                (IMessengerConversationWndAdvanced)pIMWindow;

            if (((IMessengerConversationWndAdvanced)pIMWindow).HWND == windowHandle)
            {
                convWindow = pIMWindow;

                timer = new Timer(new TimerCallback(timer_Tick), null,
                    TimeSpan.FromSeconds(0), TimeSpan.FromSeconds(1));
            }
        }

Note that we check for matching window handles before doing anything - there could be multiple instances of Communicator windows in existence at the same time; we need to make sure that we are dealing with the right window.

Also note that we set our class variable convWindow to the pIMWindow object. This way, the Timer's tick event can access the window to check its History property.

Tick

       private void timer_Tick(object state)
        {
            IMessengerConversationWndAdvanced imWindow = 
                (IMessengerConversationWndAdvanced)convWindow;

            if (imWindow.History != null)
            {
                string history = imWindow.History;

                // Do what you need to do here ...


                imWindow.Close();

                timer.Change(Timeout.Infinite, Timeout.Infinite);
                timer.Dispose();
            }
        }

When the window's History property is finally not null, you can can run whatever logic you need to. In my scenario, I closed the window, set the timer to never fire again, and then disposed it. This way, the next time this happens, the timer will be reinitialized cleanly.

Tick Durations

You should set up your timer to tick at an interval that's convenient for your needs; for example it shouldn't tick again while the timer_Tick handler is still executing.

Cleaning Up

Remember that these are all COM objects that need to be disposed of property. You should use Marshal.ReleaseComObject(... to clean up when you're done.

Bill Gates Keynote at ODC 2008

gdurzi — Mon, 11 Feb 2008 18:56:00 GMT

I just got back from the Bill Gates keynote at ODC 2008 and wanted to share some tidbits.

This is the second time I've heard Bill speak, and both times I found the Q&A session to be a very valuable part of the keynote. Some conference attendees got a chance to ask Bill some questions and express some frustrations with developing around Office and SharePoint.

Here are some of the more interesting point that came out of the Q&A:

Office 14

Microsoft is hard at work on Office 14 (looks like we're skipping v13)
Office 14 will contain a major "Office in the cloud" piece where there will be web versions of programs such as Word, Excel, etc.

Bill acknowledged that these wouldn't be as feature-rich, but would contain enough functionality for the most common tasks, e.g. OWA vs. Outlook

SharePoint

He acknowledged that SharePoint 2007's success caught Microsoft a little by surprise
They're doing their best to catch up on documentation and developer tool support
Increased staffing in SharePoint product support
Future support for enabling Lists to use their own SQL tables for storage

Apple

He pointed out that a lot of effort was made to "Apple'ify" Office 2008 for the Mac
As a result, there are no plans to support things such as VBA and Ribbon extensibility in Office 2008 for the Mac
This comment came as a result of someone asking if Microsoft would eventually provide support for programming against the object model in Office 2008 for the Mac

Overall, I was impressed by how everybody who asked a question got a straight and informed answer. Well, except the host who asked: "What's up with Yahoo?"