<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Creating Solution Packages for WSS 3.0 and MOSS 2007 Deployments</title>
	<atom:link href="http://alonsorobles.com/2008/05/16/creating-solution-packages-for-wss-30-and-moss-2007-deployments/feed/" rel="self" type="application/rss+xml" />
	<link>http://alonsorobles.com/2008/05/16/creating-solution-packages-for-wss-30-and-moss-2007-deployments/</link>
	<description>technology, academia, and other tidbits from the trenches of a boggled mind</description>
	<lastBuildDate>Tue, 17 Apr 2012 03:59:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Alonso Robles / Caution When Packaging Themes for SharePoint Products and Technologies</title>
		<link>http://alonsorobles.com/2008/05/16/creating-solution-packages-for-wss-30-and-moss-2007-deployments/comment-page-1/#comment-14</link>
		<dc:creator>Alonso Robles / Caution When Packaging Themes for SharePoint Products and Technologies</dc:creator>
		<pubDate>Mon, 21 Jul 2008 19:40:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.importchaos.com/alonsorobles/?p=34#comment-14</guid>
		<description>[...] few months ago, I explained how WSS deploys and retracts solution packages. In that explanation, I explaned that the WSS run-time checks the solution manifest of the solution [...]</description>
		<content:encoded><![CDATA[<p>[...] few months ago, I explained how WSS deploys and retracts solution packages. In that explanation, I explaned that the WSS run-time checks the solution manifest of the solution [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alonso Robles / Packaging Branding and Themes for Deployment in SharePoint Environments</title>
		<link>http://alonsorobles.com/2008/05/16/creating-solution-packages-for-wss-30-and-moss-2007-deployments/comment-page-1/#comment-13</link>
		<dc:creator>Alonso Robles / Packaging Branding and Themes for Deployment in SharePoint Environments</dc:creator>
		<pubDate>Thu, 26 Jun 2008 18:09:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.importchaos.com/alonsorobles/?p=34#comment-13</guid>
		<description>[...] to create our own solution package to deploy the custom theme. For more information, I covered the creation of solution packages (WSP files) in detail in a previous post. Let&#8217;s take a quick look at the solution manifest for our theme [...]</description>
		<content:encoded><![CDATA[<p>[...] to create our own solution package to deploy the custom theme. For more information, I covered the creation of solution packages (WSP files) in detail in a previous post. Let&#8217;s take a quick look at the solution manifest for our theme [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alonso Robles / Creating a SharePoint Solution for an InfoPath Form Template Deployment</title>
		<link>http://alonsorobles.com/2008/05/16/creating-solution-packages-for-wss-30-and-moss-2007-deployments/comment-page-1/#comment-12</link>
		<dc:creator>Alonso Robles / Creating a SharePoint Solution for an InfoPath Form Template Deployment</dc:creator>
		<pubDate>Thu, 05 Jun 2008 06:19:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.importchaos.com/alonsorobles/?p=34#comment-12</guid>
		<description>[...] InfoPath browser-enabled form template deployments are easy enough to do via the InfoPath client when the template does not require administrator approval. However even when administrator approval is not required, but the SharePoint governance plan requires script-able deployments of all InfoPath forms due to quality assurance and user acceptance testing requirements we need a mechanism to package our forms in a WSS solution package. [...]</description>
		<content:encoded><![CDATA[<p>[...] InfoPath browser-enabled form template deployments are easy enough to do via the InfoPath client when the template does not require administrator approval. However even when administrator approval is not required, but the SharePoint governance plan requires script-able deployments of all InfoPath forms due to quality assurance and user acceptance testing requirements we need a mechanism to package our forms in a WSS solution package. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

