<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Just Another Web Application : developer</title><link>http://blogs.technet.com/jasbro/archive/tags/developer/default.aspx</link><description>Tags: developer</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Quickie blog post: SharePoint SDK available, quick note on discusson lists</title><link>http://blogs.technet.com/jasbro/archive/2007/08/22/quickie-blog-post-sharepoint-sdk-available-quick-note-on-discusson-lists.aspx</link><pubDate>Wed, 22 Aug 2007 07:51:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1800316</guid><dc:creator>jasbro</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jasbro/comments/1800316.aspx</comments><wfw:commentRss>http://blogs.technet.com/jasbro/commentrss.aspx?PostID=1800316</wfw:commentRss><description>&lt;P&gt;The Sharepoint SDK (officially, the "SharePoint Server 2007 SDK: Software Development Kit and Enterprise Content Management Starter Kit") is &lt;A class="" title="Sharepoint SDK" href="http://www.microsoft.com/downloads/details.aspx?FamilyId=6D94E307-67D9-41AC-B2D6-0074D6286FA9&amp;amp;displaylang=en" mce_href="http://www.microsoft.com/downloads/details.aspx?FamilyId=6D94E307-67D9-41AC-B2D6-0074D6286FA9&amp;amp;displaylang=en"&gt;downloadable from microsoft.com&lt;/A&gt;. If you develop .NET applications for SharePoint, or support said applications, then you're going to need this sooner or later. Note: it's also viewable online.&lt;/P&gt;
&lt;P&gt;the second quick note: if you plan on developing anything for MOSS 2007 that modifies discussion list posts, you're going to need to remember: updating the 'body' property of the SPListItem object is all very well, but you&amp;nbsp;may also need to update the SPListItem["TrimmedBody"] property too - this is the version of the body text which shows up in &lt;EM&gt;unquoted&lt;/EM&gt; view. This came up in a recent support case&lt;/P&gt;
&lt;P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"&gt;&lt;FONT face=Courier size=3&gt;li["Body"] = helper.DoSomethingToBodyText(li["Body"].ToString());&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"&gt;&lt;FONT face=Courier size=3&gt;li["TrimmedBody"] = helper.DoSomethingToBodyText(li["TrimmedBody"].ToString());&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoPlainText style="MARGIN: 0cm 0cm 0pt"&gt;&lt;FONT face=courier size=3&gt;li.SystemUpdate();&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;A popular thing to do with these programatically is to auto-hyperlink or auto-format&amp;nbsp;certain keywords in text - if you don't update both variables you end up with only the quoted view showing your changes.&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=1800316" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jasbro/archive/tags/developer/default.aspx">developer</category><category domain="http://blogs.technet.com/jasbro/archive/tags/sharepoint/default.aspx">sharepoint</category><category domain="http://blogs.technet.com/jasbro/archive/tags/development/default.aspx">development</category><category domain="http://blogs.technet.com/jasbro/archive/tags/sdk/default.aspx">sdk</category></item><item><title>I'm in yr Office System, Devloping yr Appz. </title><link>http://blogs.technet.com/jasbro/archive/2007/05/31/i-m-in-yr-office-system-devloping-yr-appz.aspx</link><pubDate>Thu, 31 May 2007 10:56:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1108866</guid><dc:creator>jasbro</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jasbro/comments/1108866.aspx</comments><wfw:commentRss>http://blogs.technet.com/jasbro/commentrss.aspx?PostID=1108866</wfw:commentRss><description>&lt;P&gt;&lt;A class="" href="http://msdn2.microsoft.com/en-us/office/bb497969.aspx" mce_href="http://msdn2.microsoft.com/en-us/office/bb497969.aspx"&gt;kthx&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;OK, so the nod to &lt;A class="" href="http://icanhascheezburger.com/2007/01/15/i-made-you-a-cookie/" mce_href="http://icanhascheezburger.com/2007/01/15/i-made-you-a-cookie/"&gt;Lolcats&lt;/A&gt; is&amp;nbsp;extremely cheesy and trite, but I'm in one of those moods, OK? To put it sensibly, the Microsoft Office Interactive Developer Map is now available from MSDN as a ClickOnce Application, designed with the creamy goodness of &lt;A class="" href="http://msdn2.microsoft.com/en-us/netframework/aa663326.aspx" mce_href="http://msdn2.microsoft.com/en-us/netframework/aa663326.aspx"&gt;WPF&lt;/A&gt;. Think of it as a nice clickable poster outlining Office System 2007 developer features&amp;nbsp;with which codemonkeys can get an overview of the amazing dev features Office 2007 has to offer. If you're involved with Information Worker development, even in passing, I'd recommend you grab it and have a browse around. Think of it has your animated information hub for Office Developer info. Pay special attention to the Sharepoint and Office Server System information&lt;/P&gt;
&lt;P&gt;kthxbye&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=1108866" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jasbro/archive/tags/wpf/default.aspx">wpf</category><category domain="http://blogs.technet.com/jasbro/archive/tags/developer/default.aspx">developer</category><category domain="http://blogs.technet.com/jasbro/archive/tags/Office/default.aspx">Office</category></item></channel></rss>