<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss'><id>tag:blogger.com,1999:blog-11096258</id><updated>2009-11-21T10:52:04.736+01:00</updated><title type='text'>InfoWorker Solutions</title><subtitle type='html'>When in doubt, hesitate!</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default?start-index=26&amp;max-results=25'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>211</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-11096258.post-633209695416480992</id><published>2009-11-14T17:44:00.010+01:00</published><updated>2009-11-15T11:37:48.231+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><title type='text'>MOSS WCM: Publishing Images and Thumbnails</title><summary type='text'>A rather nice SharePoint feature for standard image libraries (type 109) is that when uploading a picture, it will automatically create a thumbnail and a compressed, web friendly version of the picture in the _t and _w hidden folders. Unfortunately the MOSS WCM PublishingImages list is not an image library, but rather a document library. This is so because the published start and end date/time </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/633209695416480992/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=633209695416480992' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/633209695416480992'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/633209695416480992'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/11/moss-wcm-publishing-images-and.html' title='MOSS WCM: Publishing Images and Thumbnails'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-7526246999364250359</id><published>2009-10-14T09:49:00.003+02:00</published><updated>2009-10-17T09:53:57.116+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><title type='text'>Secure External SharePoint Sites for Anonymous Access</title><summary type='text'>As there is some blogging about exploiting unsecured SharePoint _layouts and _vti_bin pages out there, posts that don't tell you how to actually secure those pages and prevent the exploit, I thought why not just post the recommended lockdown method: Locking down Office SharePoint Server sites

It is not enough just to enable the SharePoint WCM publishing lockdown mode feature, as this only limits</summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/7526246999364250359/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=7526246999364250359' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/7526246999364250359'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/7526246999364250359'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/10/secure-external-sharepoint-sites-for.html' title='Secure External SharePoint Sites for Anonymous Access'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-1912663311435680152</id><published>2009-10-01T08:09:00.052+02:00</published><updated>2009-10-28T21:39:19.641+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Kerberos'/><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><category scheme='http://www.blogger.com/atom/ns#' term='IIS'/><title type='text'>SharePoint Farm using Kerberos on IIS7</title><summary type='text'>Kerberos is recommended as the authentication mode in SharePoint due to security, performance and not least delegation (impersonation, double-hop) reasons. I won't go into details on the benefits here, but rather point to some good resources you will need when configuring Kerberos for SharePoint. Configuration of Kerberos is not part of the SharePoint installer, except for popup boxes warning you</summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/1912663311435680152/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=1912663311435680152' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/1912663311435680152'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/1912663311435680152'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/10/sharepoint-farm-using-kerberos-on-iis7.html' title='SharePoint Farm using Kerberos on IIS7'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-7997140872789640554</id><published>2009-09-18T13:31:00.025+02:00</published><updated>2009-09-22T18:31:37.485+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><category scheme='http://www.blogger.com/atom/ns#' term='IA'/><category scheme='http://www.blogger.com/atom/ns#' term='Design'/><title type='text'>SharePoint Site Structuring: Wide vs Deep (Part II)</title><summary type='text'>In my last post, I presented a SharePoint site classification &amp; structuring scheme for realizing the information architecture (IA) structural design of your information space to facilitate content organization. SharePoint has five main content containers that can be combined to best structure the content according to your IA:
Root site-collections: container for portal, home sites 
Explicit </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/7997140872789640554/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=7997140872789640554' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/7997140872789640554'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/7997140872789640554'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/09/sharepoint-site-structure-wide-vs-deep.html' title='SharePoint Site Structuring: Wide vs Deep (Part II)'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_VhGcD5-4xdY/Srj7axDZdII/AAAAAAAAAOA/COtG1d_jp3U/s72-c/SharePoint+msc+vs+wide+and+deep+site+structures.jpg' height='72' width='72'/><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-7770415554249864717</id><published>2009-09-06T11:27:00.043+02:00</published><updated>2009-09-22T18:33:12.219+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><category scheme='http://www.blogger.com/atom/ns#' term='IA'/><category scheme='http://www.blogger.com/atom/ns#' term='Design'/><title type='text'>Classification and Structuring of SharePoint Sites (Part I)</title><summary type='text'>As part of my work as a SharePoint architect, I almost always run into poorly designed and structured SharePoint solutions. Mostly because consultants hardly ever seems to read and really understand the Technet SharePoint Site Structure Planning and the SharePoint Logical Design and Architecture guidelines or do any information architecture (IA) analysis. What is needed is a simple 'four category</summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/7770415554249864717/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=7770415554249864717' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/7770415554249864717'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/7770415554249864717'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/09/classification-and-structuring-of.html' title='Classification and Structuring of SharePoint Sites (Part I)'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_VhGcD5-4xdY/Srj540POSVI/AAAAAAAAANw/puQPltS99lM/s72-c/SharePoint+classification+of+sites.jpg' height='72' width='72'/><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-6548048965941466166</id><published>2009-08-31T18:05:00.007+02:00</published><updated>2009-08-31T20:47:23.036+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Other'/><title type='text'>Puzzlepart - Exciting Times Ahead</title><summary type='text'>Today was my last day as an MSFT FTE, tomorrow I'm co-founder and partner at Puzzlepart - as the second person in the company after my old colleague Mads Nissen.At Puzzlepart we will continue our joint SharePoint adventure. Together we have delivered quite a few SharePoint and MSCRM solutions, such as this case study shown by Steve Ballmer himself at the 2005 business summit. As you can see from </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/6548048965941466166/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=6548048965941466166' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/6548048965941466166'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/6548048965941466166'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/08/puzzlepart-exciting-times-ahead.html' title='Puzzlepart - Exciting Times Ahead'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-8757226508738129353</id><published>2009-08-17T08:12:00.011+02:00</published><updated>2009-08-17T16:03:51.970+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='DDD'/><category scheme='http://www.blogger.com/atom/ns#' term='SOA'/><category scheme='http://www.blogger.com/atom/ns#' term='Modeling'/><title type='text'>DDD Lessons Learnt: Fat Domain Model, Concrete Aggregate Entity</title><summary type='text'>It's been five years since Eric Evans' classic book Domain-driven design: tackling complexity in the heart of software was published. Last week two interesting articles came out; What I've learned about DDD since the book by Eric himself and Domain Models: Employing the Domain Model Pattern by Udi Dahan. They both talk of lessons learnt about some of the concepts of domain-driven design (DDD).Udi</summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/8757226508738129353/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=8757226508738129353' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/8757226508738129353'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/8757226508738129353'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/08/ddd-lessons-learnt-fat-domain-model.html' title='DDD Lessons Learnt: Fat Domain Model, Concrete Aggregate Entity'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-2654778382389494571</id><published>2009-07-02T08:30:00.031+02:00</published><updated>2009-07-06T20:27:19.129+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='ContentType'/><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><title type='text'>List Content Type Fields &amp; Forms: CAML vs Code</title><summary type='text'>In a feature based site definition I recently made, I had a site content type hierarchy with a base content type and two child content types defined in a feature. The child types inherits their site columns and display/edit/new form from their parent.Another dependent feature contained a list definition and a provisioned list instance that would reference the two child site content types and thus</summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/2654778382389494571/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=2654778382389494571' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/2654778382389494571'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/2654778382389494571'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/07/sharepoint-list-content-type-forms.html' title='List Content Type Fields &amp; Forms: CAML vs Code'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_VhGcD5-4xdY/Sktd4ORY9ZI/AAAAAAAAAMI/Um_80Wh0mS8/s72-c/site_contenttypes.jpg' height='72' width='72'/><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-5420792109104757213</id><published>2009-07-01T10:00:00.028+02:00</published><updated>2009-11-14T23:27:21.639+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><category scheme='http://www.blogger.com/atom/ns#' term='IA'/><category scheme='http://www.blogger.com/atom/ns#' term='UX'/><title type='text'>Review: Building the SharePoint User Experience</title><summary type='text'>Lately I've been reading Building the SharePoint User Experience by fellow Norwegian Bjørn Furuknap, and it is an easy read even if it covers "under the hood" aspects of SharePoint UX such as list definitions, site definitions, content types, custom fields, features, stapling, onet.xml, and the beast itself: CAML. Don't be fooled by the term UX, this book is not about doing SharePoint design </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/5420792109104757213/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=5420792109104757213' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/5420792109104757213'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/5420792109104757213'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/07/review-building-sharepoint-user.html' title='Review: Building the SharePoint User Experience'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-5176770448487301548</id><published>2009-06-16T13:48:00.018+02:00</published><updated>2009-06-25T19:43:31.749+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><category scheme='http://www.blogger.com/atom/ns#' term='jQuery'/><title type='text'>SharePoint jQuery: Managing Scripts</title><summary type='text'>In the two previous posts, I've shown some jQuery scripts for manipulating the SharePoint user interface by adding the scripts directly as source text in a Content Editor Web Part (CEWP). This is, however, not a good way of adding the scripts to pages considering maintenance and sharing of the provided functionality across multiple pages. Just think of making a correction to the generic scrolling</summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/5176770448487301548/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=5176770448487301548' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/5176770448487301548'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/5176770448487301548'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/06/sharepoint-jquery-managing-scripts.html' title='SharePoint jQuery: Managing Scripts'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_VhGcD5-4xdY/SjecDVmL17I/AAAAAAAAALw/Q_vJd0pcQRc/s72-c/jquery_script_locations.JPG' height='72' width='72'/><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-7787072075584089728</id><published>2009-06-16T13:24:00.005+02:00</published><updated>2009-06-19T11:51:19.892+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><category scheme='http://www.blogger.com/atom/ns#' term='jQuery'/><title type='text'>SharePoint Site Relative CEWP Included Script</title><summary type='text'>This post is about injecting site relative JavaScript include files in SharePoint using CEWP. It is not about injecting JavaScript files using the server-side ASP.NET script manager or any other server-side mechanism.We all know that the src attribute of the &lt;script&gt; element is either page relative or server relative; or God forbid, absolute. You cannot use the tilde (~) to make the URL site </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/7787072075584089728/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=7787072075584089728' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/7787072075584089728'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/7787072075584089728'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/06/sharepoint-site-relative-cewp-included.html' title='SharePoint Site Relative CEWP Included Script'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-9047551322120772858</id><published>2009-06-12T09:18:00.009+02:00</published><updated>2009-06-18T17:37:37.083+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><category scheme='http://www.blogger.com/atom/ns#' term='jQuery'/><title type='text'>SharePoint jQuery: Scrolling View with Frozen Header</title><summary type='text'>SharePoint lists that contain a lot of numeric data type columns can be hard to look at when the column headers scroll out of view. Such lists are typically created by moving data entry into SharePoint from Excel, where users could easily freeze the header row. As I showed back in 2005 for ASP.NET datagrids, you can achieve a frozen header row also for HTML tables by applying a simple CSS </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/9047551322120772858/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=9047551322120772858' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/9047551322120772858'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/9047551322120772858'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/06/sharepoint-jquery-scrolling-view-with.html' title='SharePoint jQuery: Scrolling View with Frozen Header'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_VhGcD5-4xdY/SjjDktR5rnI/AAAAAAAAAMA/R4oJLSU4T_E/s72-c/scrolling_list_frozen_header.jpg' height='72' width='72'/><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-3331656261484625386</id><published>2009-06-10T13:26:00.025+02:00</published><updated>2009-06-18T17:37:37.084+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><category scheme='http://www.blogger.com/atom/ns#' term='jQuery'/><title type='text'>SharePoint jQuery: Setting View Column Width</title><summary type='text'>A very common request for changes to SharePoint list views is how to set the column width. This is not possible to do using the ootb "List Settings", and the common suggested fix is to use SharePoint Designer (SPD) and convert the view into an "XSLT Data View": How can I manage columns widths in list views? Most large companies do, however, prevent the use of SPD.With jQuery there is no need to </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/3331656261484625386/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=3331656261484625386' title='9 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/3331656261484625386'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/3331656261484625386'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/06/sharepoint-jquery-setting-td-column.html' title='SharePoint jQuery: Setting View Column Width'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>9</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-656875621535957882</id><published>2009-06-07T12:35:00.034+02:00</published><updated>2009-08-17T18:57:42.181+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='ES-EWA'/><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><category scheme='http://www.blogger.com/atom/ns#' term='Office1x'/><category scheme='http://www.blogger.com/atom/ns#' term='Enterprise2.0'/><title type='text'>Excel Solutions in SharePoint</title><summary type='text'>In my last post, I talked about the situational solutions that users themselves has created in Excel - and how these isolated workbook islands counters knowledge management and the ability to leverage the information and people ecosystem of your company. To subject the Excel workbook sprawl to shared knowledge management, you must provide Excel-style services as components of your Enterprise 2.0 </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/656875621535957882/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=656875621535957882' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/656875621535957882'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/656875621535957882'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/06/excel-solutions-in-sharepoint.html' title='Excel Solutions in SharePoint'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_VhGcD5-4xdY/Si4HCj6ie0I/AAAAAAAAALI/Ms46LPy5Rhc/s72-c/moss_excel_taskpane.JPG' height='72' width='72'/><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-8664542921692851983</id><published>2009-05-23T09:52:00.015+02:00</published><updated>2009-06-18T17:37:37.086+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='ES-EWA'/><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><category scheme='http://www.blogger.com/atom/ns#' term='Enterprise2.0'/><title type='text'>SharePoint: Excel Long-Tail Knowledge Management</title><summary type='text'>In these uncertain times, push systems for knowledge sharing and management are giving less results than before due to the limited planning visibility into the future - it is just becoming too hard to provide the users with the tools they need before they need it. The knowledge workers have turned to pull systems to create situational software solutions to assist in solving their business </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/8664542921692851983/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=8664542921692851983' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/8664542921692851983'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/8664542921692851983'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/05/sharepoint-excel-long-tail-knowledge.html' title='SharePoint: Excel Long-Tail Knowledge Management'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-4728400294124209833</id><published>2009-04-26T17:13:00.004+02:00</published><updated>2009-07-02T08:55:34.025+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='ContentType'/><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><category scheme='http://www.blogger.com/atom/ns#' term='IA'/><title type='text'>SharePoint Governance Guidelines</title><summary type='text'>The SharePoint Products and Technologies governance checklist guide on the Technet SharePoint Governance Resource Center is very popular among our customers. It covers aspects from architectural planning, roles and policies, to operational practices.To complement this official checklist, I've collected some more concrete guidelines that my customers often request when getting started with MOSS. </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/4728400294124209833/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=4728400294124209833' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/4728400294124209833'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/4728400294124209833'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/04/sharepoint-governance-guidelines.html' title='SharePoint Governance Guidelines'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-6034443092692367581</id><published>2009-03-26T11:03:00.011+01:00</published><updated>2009-06-18T17:37:37.088+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Web2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='SharePoint'/><category scheme='http://www.blogger.com/atom/ns#' term='IA'/><category scheme='http://www.blogger.com/atom/ns#' term='Enterprise2.0'/><title type='text'>Emergent vs Deliberate, Push vs Pull</title><summary type='text'>The Web 2.0 "Emergent vs Deliberate" struggle for control is not new, the discussions are at least a couple of years old. However, it is still very applicable inside the enterprise due to the lack of Web 2.0 features in business applications. Add to this that Information Architects - strongly supported by document and records management experts, prefer controlled vocabularies over social freeform</summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/6034443092692367581/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=6034443092692367581' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/6034443092692367581'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/6034443092692367581'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/03/emergent-vs-deliberate-push-vs-pull.html' title='Emergent vs Deliberate, Push vs Pull'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_VhGcD5-4xdY/SctUbjzKl4I/AAAAAAAAAKg/2aqfjm8z7OM/s72-c/push_vs_pull_systems.jpg' height='72' width='72'/><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-3553401246720884330</id><published>2009-03-25T13:20:00.011+01:00</published><updated>2009-03-25T14:16:45.204+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Web2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='IA'/><category scheme='http://www.blogger.com/atom/ns#' term='Enterprise2.0'/><title type='text'>Enterprise 2.0 Zen: Emergent Crystalization of Quality</title><summary type='text'>I am a huge fan of the book "Zen and the Art of Motorcycle Maintenance" which looks into the metaphysics of quality. A central part of this is "crystalization" driven by quality, you have to have a sense of what's good and what's not. Crystalization separates useful from meaningless in perceived information, it applies quality.The elevator pitch of Enterprise 2.0 is that it is freeform, emergent,</summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/3553401246720884330/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=3553401246720884330' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/3553401246720884330'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/3553401246720884330'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/03/enterprise-20-zen-emergent.html' title='Enterprise 2.0 Zen: Emergent Crystalization of Quality'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-8300648569924195476</id><published>2009-03-11T11:42:00.009+01:00</published><updated>2009-03-12T09:19:24.622+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Messaging'/><category scheme='http://www.blogger.com/atom/ns#' term='WCF'/><title type='text'>WCF Queued Dual Router Updated</title><summary type='text'>I've updated the source for the WCF Queued Dual HTTP Request Response Router to now support sending out-of-band fault and notification messages back to the consumer. The added unified fault handling support for router and services is using ChannelFactory&lt;T&gt; were T is IOutputChannel to support generic one-way channel shapes. The same generic WCF channel shape is used for sending notification </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/8300648569924195476/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=8300648569924195476' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/8300648569924195476'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/8300648569924195476'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/03/wcf-queued-dual-router-updated.html' title='WCF Queued Dual Router Updated'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_VhGcD5-4xdY/SbjFWQlK7kI/AAAAAAAAAKY/eRjsRt0Jajg/s72-c/WCF_queued_dual_http_router.jpg' height='72' width='72'/><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-5693848386243169039</id><published>2009-02-25T21:50:00.019+01:00</published><updated>2009-03-11T22:10:13.019+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Messaging'/><category scheme='http://www.blogger.com/atom/ns#' term='WCF'/><title type='text'>WCF Queued Dual HTTP Request Response Router</title><summary type='text'>There are a lot of examples available for how to make WCF-based publish/subscribe messaging solutions, but not very many thay provides a simple queued dual HTTP request-response router. IDesign provides the queued Response Service from Juval Löwy's book Programming WCF Services, which provides a feature rich set of WCF goodies. Recommended. I've used it in combination with Sasha Goldshtein's </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/5693848386243169039/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=5693848386243169039' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/5693848386243169039'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/5693848386243169039'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/02/wcf-queued-dual-http-request-response.html' title='WCF Queued Dual HTTP Request Response Router'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-5736696618021868373</id><published>2009-02-20T08:42:00.004+01:00</published><updated>2009-02-20T09:45:04.417+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Messaging'/><category scheme='http://www.blogger.com/atom/ns#' term='Contracts'/><category scheme='http://www.blogger.com/atom/ns#' term='WCF'/><title type='text'>WCF: Message Headers and XmlSerializerFormat</title><summary type='text'>Sometimes you need to use the classic XmlSerializer due to interoperability or when doing schema first based on XSD contracts that contains e.g. XML attributes in complexTypes. I've used the [XmlSerializerFormat] switch on services many times without any problems, but recently I had to make use of a custom header - and that took me quite some time to get working.This is the wire format of the </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/5736696618021868373/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=5736696618021868373' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/5736696618021868373'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/5736696618021868373'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/02/wcf-message-headers-and.html' title='WCF: Message Headers and XmlSerializerFormat'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-1103460298490030078</id><published>2009-02-12T20:34:00.032+01:00</published><updated>2009-08-17T11:29:14.621+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SOA'/><category scheme='http://www.blogger.com/atom/ns#' term='CIM'/><category scheme='http://www.blogger.com/atom/ns#' term='ECDM'/><category scheme='http://www.blogger.com/atom/ns#' term='Modeling'/><title type='text'>SOA CIM: Common Information Model</title><summary type='text'>As I've written about before, there is a lot of confusion and different interpretations of what a "Common Information Model" (CIM) is. The most common reification of CIM is to imply that it is the same concept as in chapter 4 "XML: The Foundation for Business Data Integration" in David Chappell's seminal book Enterprise Service Bus from 2004. Dave describes the need for having a common XML data </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/1103460298490030078/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=1103460298490030078' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/1103460298490030078'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/1103460298490030078'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/02/cim-common-information-model.html' title='SOA CIM: Common Information Model'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_VhGcD5-4xdY/SZR9eqYtUHI/AAAAAAAAAJ4/pPq_O9pbURk/s72-c/SOA_CIM_Mike_Rosen_18aug2006.jpg' height='72' width='72'/><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-7792860422639707636</id><published>2009-02-10T08:04:00.022+01:00</published><updated>2009-08-17T11:29:14.622+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Contracts'/><category scheme='http://www.blogger.com/atom/ns#' term='DDD'/><category scheme='http://www.blogger.com/atom/ns#' term='SOA'/><category scheme='http://www.blogger.com/atom/ns#' term='CIM'/><category scheme='http://www.blogger.com/atom/ns#' term='ECDM'/><category scheme='http://www.blogger.com/atom/ns#' term='Design'/><category scheme='http://www.blogger.com/atom/ns#' term='Modeling'/><title type='text'>SOA: Business Event Message Models</title><summary type='text'>InfoQ has published an article about SOA Message Type Architecture by Jean-Jacques Dubray. The article shows how to model 'message type' artifacts based on an enterprise common data model using a DSL, and also outlines how the modeled artifacts can be used to generate XML schemas for use in your service contracts. The message type DSL is not for modeling messages, it is just for modeling the </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/7792860422639707636/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=7792860422639707636' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/7792860422639707636'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/7792860422639707636'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/02/soa-business-event-message-models.html' title='SOA: Business Event Message Models'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_VhGcD5-4xdY/SZacVX1gXcI/AAAAAAAAAKA/-6t1xCt-OUk/s72-c/service_versioning_composability_schema_semantics_v3.jpg' height='72' width='72'/><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-1010701486467956207</id><published>2009-02-01T01:15:00.015+01:00</published><updated>2009-06-20T17:51:16.478+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Messaging'/><category scheme='http://www.blogger.com/atom/ns#' term='Contracts'/><category scheme='http://www.blogger.com/atom/ns#' term='SOA'/><category scheme='http://www.blogger.com/atom/ns#' term='Schema'/><category scheme='http://www.blogger.com/atom/ns#' term='REST'/><category scheme='http://www.blogger.com/atom/ns#' term='Virtualization'/><category scheme='http://www.blogger.com/atom/ns#' term='WSDL'/><category scheme='http://www.blogger.com/atom/ns#' term='Versioning'/><title type='text'>Service Compatibility - A Primer</title><summary type='text'>In a comment on the InfoQ article Contract Versioning, Compatibility and Composability about my definition of service forwards and backwards compatibility, the problem of talking about compatibility of services compared to the definition of schema compatibility is acknowledged.The "problem" is that a service version that is compatible with the specifications of older versions of the service, can </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/1010701486467956207/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=1010701486467956207' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/1010701486467956207'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/1010701486467956207'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/02/service-compatibility-primer.html' title='Service Compatibility - A Primer'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_VhGcD5-4xdY/SYRVWYEF8-I/AAAAAAAAAJg/Lw44v06uM38/s72-c/backwards_compatibility_v2_kjellsj.jpg' height='72' width='72'/><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-11096258.post-6639392821853100642</id><published>2009-01-19T20:45:00.005+01:00</published><updated>2009-01-26T17:52:09.560+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='ADO.NET'/><category scheme='http://www.blogger.com/atom/ns#' term='Transactions'/><title type='text'>A few System.Transactions gotchas</title><summary type='text'>I'm currently at a customer reviewing database blocking problems, and I thought I should document some less known gotchas when using System.Transactions. But first an improvement.We all know about the famous "promotion" from LTM transactions to the expensive two phase commit DTC transactions when using/opening/enlisting more than one connection to a SQL Server 2005 database within a transaction </summary><link rel='replies' type='application/atom+xml' href='http://kjellsj.blogspot.com/feeds/6639392821853100642/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=11096258&amp;postID=6639392821853100642' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/6639392821853100642'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/11096258/posts/default/6639392821853100642'/><link rel='alternate' type='text/html' href='http://kjellsj.blogspot.com/2009/01/few-systemtransactions-gotchas.html' title='A few System.Transactions gotchas'/><author><name>Kjell-Sverre Jerijærvi</name><uri>http://www.blogger.com/profile/13654217591841196465</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='13668916778551756586'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry></feed>