Mads Nissen

I've created a InfoPath form designed to be highly movable. Somewhat against my own principles these forms have more than a few dataconnections and I wanted the reconfiguration effort to be minimal, preferrably zero, when the form was moved from one Sharepoint site to the next.

We've been working for a while resolving YASQ with a customer. While working on it we actually ran into the problem ourselves on the Objectware AS/Itera portal. I contacted my friend in need Daniel McPherson on the Elite Lookingood EXtraordinary Sharepoint Immediate Response team and he conincidentally was working on the same issue and had put togehter a repro for the issue:

The language bug I've been tracking for a long time have been resolved by Microsoft. The problem is that they haven't made the fix generally available and currently I am currently only allowed to share the fix with my customers.

I'm currently talking about Smart Clients around Norway and I've been focusing on the architectural aspects of Smart Client technology. Recently Clemens posted about much the same topic.

Yesterday I held three sessions at the quartely Microsoft Days (Microsoftdagene) event in Oslo. In three sessions we covered Smart Clients in the Service Oriented Architecture, todays technologystack, and the features of the upcoming technology stack from Microsoft with focus on VSTO 2005 and Windows Forms 2.0.

UPDATE: The scenario gets less and less impossible:-)

Today we've had the pleasure of having Anders Hejlsberg on a visit to Oslo and he's been touring press, academic foras, NNUG, JavaBin, and a Microsoft hosted event. My colleague Trond Brande followed mr. Hejlsberg with two talks on upcoming SQL Server 2005, and I finished the day at Folkets Hus with two sessions on Best Practices for development, and Visual Studio Team System.

For a recent project we had to discard Visual Source Safe for source control because we needed remote access to our build system. Previously we've been using SourceGears Source Off Site to access VSS, but this time we noticed that SourceGear had a pricing model that made their SQL Server based source control system Vault a cheaper option. In the process we also considered moving to CVS which was available internally, but discarded it due to the developers incompetence (myself included) on the subject.