<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>SharePoint Solution Packages &amp;quot;No More Xcopy&amp;quot;</title><link>http://blogs.msdn.com/ekraus/archive/2008/06/18/sharepoint-solution-packages-no-more-xcopy.aspx</link><description>I talk to many developers who are still using "xcopy" to deploy some of their SharePoint files to the 12 Hive (especially trust files and custom stsadm commands). It is well known that the manifest.xml file within a WSP can be configured to deploy assemblies</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Pregnant Man &amp;raquo; SharePoint Solution Packages &amp;#8220;No More Xcopy&amp;#8221;</title><link>http://blogs.msdn.com/ekraus/archive/2008/06/18/sharepoint-solution-packages-no-more-xcopy.aspx#8619809</link><pubDate>Thu, 19 Jun 2008 05:08:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8619809</guid><dc:creator>Pregnant Man &amp;raquo; SharePoint Solution Packages &amp;#8220;No More Xcopy&amp;#8221;</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://wordnew.acne-reveiw.info/?p=209"&gt;http://wordnew.acne-reveiw.info/?p=209&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>