#region /* mads's thoughts */

GameCamp Oslo - Inspirational Boosting

madsn — Sat, 27 Sep 2008 06:25:00 GMT

Yesterday I left my dayjob early to go with my brother Marius to the Oslo GameCamp at my former school NITH . I really wanted to get a better understanding of game programming and my brother (who is 18) is considering getting more into programming so...(read more)

How to drive value from Sharepoint and the Microsoft platform

madsn — Fri, 26 Sep 2008 08:19:00 GMT

Focus on asking the right business questions, let 3rd party product vendors supply the missing parts, and configure and customize the platform and products and with an aim for business solutions with web 2.0 bliss....(read more)

How to sum up 2 years

madsn — Thu, 25 Sep 2008 09:51:00 GMT

This is one of the "it's been a long time since my last blogpost" type posts and I'm about to confess to my non-blogging sins (and I'll try to make it short), before I move on to talk about my new venture with Puzzlepart . The past 4,5 years I've been...(read more)

Building Web Application Projects with CCNET

madsn — Mon, 19 Jun 2006 13:53:00 GMT

One of the things about Visual Studio 2005 I disapprove of the most is the way features related to your project are stuffed into the local devmachine environment under Program Files. Among other things the coming GAT (guidance automation toolkits) work...(read more)

More VSTO Deployment - AppCheck and PIACheck compiled

madsn — Wed, 03 May 2006 10:46:00 GMT

A while ago Microsoft released a walkthrough for VSTO deployment to, as Misha puts it; "not remove the pain but help controlling it". The walkthrough covers all my (less structured) instructions, and improves on security aspects.

However the article does provide you with a fair amount of work. The security part adds strong-name based evidence for assemblies which is absolutely required from a security perspective. However, the samples does not support multi-assembly deployments so you'll need to write this up yourself. I'll look into using Assembly.GetReferencedAssemblies() later on to see if that will solve this problem.

Furthermore you get native checking utils for common prereqs. These are not compiled however and Aerodrome has posted a compiled version. Although these exe's (PIACheck.exe and AppCheck.exe) works nicely if you've got the .NET Framework preinstalled, they will fail if not. Probably because they're compiled in managed C++, and not the way instructed in the MSDN article. We've made a working set available here (courtesy of compilation genious Øystein Garshol).

Finally I have to point out once more the weak design of the prerequisite package structure. The prerequisite definitions are fundamentally a part of any solution and should at least be copied into the solution or setup project filestructure when used to enable inclusion in sourcecontrol and automated builds. I would sure like to know how Microsoft approaches this problem using WiX or other tools.

And to all of you who haven't deleted my blog from your blogroll: I'm back:-)

MSCRM 3.0 and the VSTO for MSCRM 3.0 Toolkit

madsn — Sat, 03 Dec 2005 13:52:00 GMT

Read about the upcoming VSTO Toolkit for MSCRM 3.0 at Kjell-Sverres blog. Beeing Objectwares MSCRM guru KSJ also have started writing about general 3.0 topics. Keep watching if you're in the MSCRM space.

Validating Sharepoint filenames on upload

madsn — Thu, 17 Nov 2005 08:28:00 GMT

Some characters are legal for FAT or NTFS files but illegal for files in Sharepoint documentlibraries. Using the regular upload UI for Sharepoint you'll encounter a rather unpleasant validation error when uploading a file with funky characters. Using the object model will give you a good ole' exception.

I've seen a lot of approaches to solving this problem, and implemented a couple myself. Last night I noticed a method on the SPEncode static class that enabled a clean approach to the problem (updated for double punctuation mark problem):

private string CleanForUrlAndFileNameUse(string dirtyFileName)

{

char[] dirtyChars = dirtyFileName.ToCharArray();

foreach (char c in dirtyChars)

{

if (!SPEncode.IsLegalCharInUrl(c))

{

dirtyFileName = dirtyFileName.Replace(c.ToString(), "");

}

// Spaces are not appreciated

dirtyFileName = dirtyFileName.Replace(" ", "");

// double punctuation marks causes validation error

while(dirtyFileName.IndexOf("..") != -1)

dirtyFileName = dirtyFileName.Replace("..", ".");

return dirtyFileName; // now clean:-)

}

Refresh page after edit in InfoPath

madsn — Tue, 01 Nov 2005 08:26:00 GMT

When using InfoPath for editing data in you webapplications you run into a couple of tricky situations when beeing used to plain webdevelopment. One of these scenarios is when you want your webpage to refresh after having edited a record in some datasource with InfoPath. Typically you've implemented a view webpage and edit with InfoPath.

This sounds pretty uncomplicated, and I guess it is, but still it took me quite a while to figure out.

My first attempt was to use standard web techniques like opening a browser window pointing to the infopath form modally with showModalDialog and refreshing the hostpage on return. No luck. I was thinking about creating a custom hostpage utilizing iframes to open the document much like a lot of people do to handle pdfs, but I really don't like adhoc host'ish pages in my solution.

I also considered going all the way and serve my Infopath documents dynamically, but that would have been to big of a change to my current solution.

I went back and studied how the Sharepoint SDK suggests to solve this problem. Sharepoint makes use of a clientside component (INLAUNCH.DLL) to open InfoPath documents. The control is called OpenXMLDocuments. From the documentation I adopted the RefreshOnFocus approach from the Create sample and tried to modify the Edit sample with it to get the refresh. Problem was that InfoPath slightly lost focus during load of the XML document which forced a too early refresh of the hostpage when using the EditDocument2 method directly.

Then I read Westins blog and got the idea to se exactly what Sharepoint does on the "Edit in Microsoft Office Infopath" button. Westin also describes how to launch an InfoPath form from a Sharepoint page but this only includes create which seems to work slightly different from edit.

Adopting the call from the "Edit in Microsoft Office Infopath" button and combining it with the RefreshOnFocus approach lead me to the following working solution for refreshing a webpage after editing in InfoPath.

function RefreshOnFocus()

{

window.location.href = window.location;

}

function showInfopathAndRefreshWhenFinished(url)

{

window.onfocus = RefreshOnFocus;

editDocumentWithProgID2(url,'InfoPath.Document','SharePoint.OpenXMLDocuments');

}

</script>

Be aware that the clientside control must be present for this to work, but I assume it is installed with InfoPath (anyone care to assert this assumption regarding INLAUNCH.DLL?). The editDocumentWithProgID2 method is defined in the standard Sharepoint script includes.

Complete set of Custom Prerequisites available

madsn — Wed, 26 Oct 2005 17:18:00 GMT

Seems like VSTO Outlook deployment just got easier. I now have Custom Prerequisites for Office 2003 (SP2), Outlook 2003 (SP2), Office 2003 PIA and the Visual Studio Tools for Office 2005 Runtime ready.

I got some feedback from the community on my previous post and I've updated my article with my findings and also a download for the prerequisite definitions for Visual Studio 2005.

VSTO Outlook: the Complete Setup Solution

Please provide feedback on this if you find bugs or points of improvement.

VSTO Outlook: The complete deplyment solution

madsn — Fri, 14 Oct 2005 16:30:00 GMT

This week has been all about the pain of client deployment of our VSTO solution. I've written a summary which I hope will be the start of the complete solution for idiot-proof installs of Outlook plugins. I'm not quite there yet but I feel I'm pretty close.

Read it here!

Input and feedback is very welcome!

Also check out Peters blog for VSTO content and the MSDN VSTO Forums.

Recycle Bin / Undelete for Document Libraries finally solved

madsn — Fri, 07 Oct 2005 08:03:00 GMT

Last week I met Todd from Mindsharp in Seattle and he told me that he'd just created a purely client side solution to the whole undelete / recycle bin problem with Sharepoint document libraries. Several solutions have been posted to address this issue in the past, amongst others Max and Erics article in MSDN Mag.

The beauty of Todds solution is it simplicity. Todd has solved everything from the clientside and wrapped it all up in a list template (.stp) file.

In addition to supply undelete features (and even right-shift key integration!!) he also adds the bonus of multitemplate document creation.

Giant kudos to Todd for this excellent piece of Sharepoint/javascript voodoomagic. In my opinion this is the final solution for undelete until WSS v3 arrives.

Get it here!

InfoPath DropDown List doesn't match on items in list

madsn — Thu, 06 Oct 2005 12:30:00 GMT

When populating InfoPath DropDown lists with values and then binding the dropdown to a field in your main datasource you'll sometimes see the bound value instead of its corresponding text value in the dropdown on load. It seems slightly confusing given that the entry containing your bound value is actually in the list, but it doesn't match.

Most likely this is a string casing problem. I've got a dropdown bound to a Sharepoint (WSS) UserGroup service and bind the value to @LoginName. These values are typically DOMAIN\login.name. My main datasource however, lowercases all reference variables to avoid any confusion. Since I don't control the formatting done by the Sharepoint service my best bet is to lowercase the values of the @LoginName attributes in my secondary datasource.

First off I got excited by this post on the InfoPath Blog which feels a bit like calling C# or javascript code from regular XSLT transformations. The blog describes calling code to evaluate conditions, not setting DOM values, and furthermore there are no events you can respond to in order to call the code that will manipulate your secondary datasource values and setting them toLower.

Since I query my UserGroup service on form load, and this occurs before the Load event in script I was able to perform toLower (or more precicely toLowerCase()) in the load event like this:

var objXMLNodes = XDocument.GetDOM("UserService").selectNodes(//@LoginName);
for(i = 0; i < objXMLNodes.length; i++)
{
objXMLNodes(i).text = objXMLNodes(i).text.toLowerCase();
}

WebBrowser control and InvokeScript

madsn — Fri, 23 Sep 2005 08:24:00 GMT

This is a little code nugget I planned to blog about a while ago, but forgot, so my recap and reasoning is not a 100% but hopefully it might be of help to someone struggelig with making the System.Windows.Forms.WebBrowser control execute scripts programatically.

I started out using the WebBrowser.InvokeScript method to force execution of clientside scripts in the page that was loaded in my WebBrowser control:

HtmlWindow win = doc.Window;
doc.InvokeScript("Update_UI_From_Values();");

This is where my reasoning is not complete (because i didn't bother to actually reproduce the original problem..), but basically it didn't work as expected. After some Reflector action I figured out that the mshtml.IHTMLWindow2.execScript method wasn't actually directly mapped into the new WebBrowser APIs and I figured I'd give it a go and add a reference to Microsoft.mshtml.dll (COM component Microsoft HTML Object Library):

mshtml.IHTMLWindow2 win = (mshtml.IHTMLWindow2)propertyEditorWebBrowser.Document.Window.DomWindow;
win.execScript("Update_UI_From_Values();", "javascript");

This had the desired effect and the script executed. Too bad the managed option didn't do the job.

Error using VSTO 2005 Outlook Addin with VS2005 RC1

madsn — Thu, 22 Sep 2005 12:29:00 GMT

Just installed Visual Studio 2005 RC1 and reinstalled Visual Studio Tools for Office 2005 Outlook on top to continue working on my Outlook Add-in. When trying to cast a MailItem object i recieved the following error:

System.InvalidCastException: Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.Office.Interop.Outlook.MailItem'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{00063034-0000-0000-C000-000000000046}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE))..

Seems like something didn't register properly and after performing the following operation from the Visual Studio 2005 Command Prompt (in a folder containing the dll) I was back up and running:

regasm Microsoft.Office.Interop.Outlook.dll

Temporary Release of Outlook Plugin code

madsn — Tue, 23 Aug 2005 11:00:00 GMT

This summer I got the opportunity to demo a VSTO Outlook plugin at TechEd in Amsterdam. The demo was done on a prototype made as a proof-of-concept for a customer in the preceeding weeks (not actually the night before the demo:-). The prototype was accepted and development for production was planned to the first weeks of august.

Unfortunately this has been postponed, so to accomodate those of you out there who wants to check out the code I'm now releasing the prototype codebase.

I would like to stress that this was developed as a proof-of-concept. Documentation is less than poor, code quality is quite frankly very close to embarrassing, but it runs. Use it to get an idea of how it might be done.

The future plan for the plugin has evolved. We're currently looking into creating a very robust "Sharepoint Favorites System" to be able to keep track of favorite sharepoint sites and import such links from both sharepoint lists (online) and possibly internet explorer favorites. We're looking at keeping an offline cache of favorites and also enable offline moving of mail to Sharepoint Favorites including metadatahandling.

As you may well understand, a rewrite is on the way. Hopefully I will be able to publish this solution on GotDotNet or SourceForge, but no timeframe is available at the moment.

The prototype includes code snippets from the SharePad project courtesy of ILG and Microsoft, specifically for document property handling.

The VS.NET 2005 solution and source code is available here. Please use for reference and if you have ideas or suggestions please contact me. The more people interested the sooner I'll establish the project publicly.