<?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>The risks around SharePoint application deployment</title><link>http://blogs.technet.com/josebda/archive/2007/03/11/the-risks-around-sharepoint-application-deployment.aspx</link><description>SharePoint is growing in popularity, partially due to its great model for describing and deploying packaged applications. This is especially true in the latest v3 or 2007 release, with the introduction of the "solution" deployment. However, if you're</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>http://virtual-generations.com/2007/03/12/a-couple-of-sharepoint-links/</title><link>http://blogs.technet.com/josebda/archive/2007/03/11/the-risks-around-sharepoint-application-deployment.aspx#718159</link><pubDate>Fri, 30 Mar 2007 09:45:59 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:718159</guid><dc:creator>TrackBack</dc:creator><description /></item></channel></rss>