SharePoint 2007

As the title should give away a minor trick to clean up your HTML output of your XLST, since when you are working with namespaces the HTML output based on a XML file will most probably look ‘crap’ containing a! lot of unnecessary info you don’t need to be outputted. ...

Most of you may know the popular posts on jquery and the use of it in SharePoint by Jan Tielens (he actually made a very nice post last day about the “search-as-you-type”. So jQuery can be used for good in SharePoint. Today we needed to create a pager on a sortable table, and since we used this tablesorter. ...

So here you found yourself clicking together a list to let users add items early in your development process, next thing you know the list is too big, and they want it to be deployed on their production servers. Or you want to upload an stp and create a list based on it (in my case; I rather upload and deploy an stp create a list based on that, then create an event receiver that added the items by code). ...

So since a week I changed from Windows Vista 32bit to a nice clean install of Windows 7 64bit, assuring myself to fully use the 4gb ram I have in this laptop, and of course switching means reinstalling all software. That brought me to the point where I decided to install the Windows Virtual PC Beta (and the XP mode of course). ...

Ever spend time trying to figure out why your nice and shiny solution file didn’t return any errors but still isn’t showing the changes you made to your masterpage or pagelayout? Last week i actually spend way to much time doing that, due to the fact that someone uploaded his masterpage to the masterpage gallery, without using the solution; thus wrecking my solution since SharePoint sets a little marker to that page, telling it that its ‘ghosted’. ...

Just some simple code this time, a minor XSLT function to change values to a nice Currency Value. Like it says, it formats a number (some var names are Dutch, sorry for that): <xsl:template name="FormatNumber"> <xsl:param name="str" /> <xsl:param name="defnadekomma" /> <xsl:variable name="newvalueS" select="string($str)"/> <xsl:value-of name="newvalue"> <xsl:if test="contains($newvalueS,',')"> <xsl:select="substring-before($newvalueS, ',')"/> <xsl:select="$newvalueS"/> </xsl:if> <xsl:variable name="nadekomma"> <xsl:if test="contains($newvalueS,',')"> <xsl:select="concat(',',substring-after($newvalueS,','))"/> <xsl:variable name="nadekommaMax"> </xsl:if> <xsl:if test="string-length($nadekomma)> 3"> <xsl:select="substring($nadekomma,1, 3)"/> <xsl:select="$defnadekomma"/> </xsl:if> <xsl:if test="string-length($newvalue)> 3"> <xsl:variable name="newvaluews"> <xsl:select="substring($newvalue,1,string-length($newvalue) – 3)"/> <xsl:select="substring($newvalue,string-length($newvalue) – 2,3)"/> <xsl:select="concat($newvaluews,$nadekommaMax)"/> <xsl:select="concat($newvalue, $nadekommaMax)"/> </xsl:variable> </xsl:if> € <xsl:variable name="FormatNumber"> <xsl:variable name="str" select="$prijs"/> <xsl:variable name="defnadekomma"select="',-'"/> </xsl:template>

So another minor post about search. Last post I explained the use of metadata property mappings, and their strength allowing you to show more information without a lot of changes. However I forgot to mention the fact that u can actually show them pretty easy in your existing search results. ...

As mentioned in the last post about Search, in the following posts there will be some more advanced features. In this post there will be some details about the your search properties (and using them in your URL). While in the next post there will be some info about the Search Result Hidden Object, that allows you to sort your complete result set (and not only by the default relevance option). ...