<?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 for Alonso Robles</title>
	<atom:link href="http://blogs.importchaos.com/alonsorobles/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.importchaos.com/alonsorobles</link>
	<description>technology, academia, and other tidbits from the trenches of a boggled mind</description>
	<pubDate>Wed, 07 Jan 2009 14:04:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on SharePoint Reading List by Alonso Robles &#187; Blog Archive &#187; WSS 3.0 and MOSS 2007 Certification</title>
		<link>http://blogs.importchaos.com/alonsorobles/2008/05/22/sharepoint-reading-list/comment-page-1/#comment-379</link>
		<dc:creator>Alonso Robles &#187; Blog Archive &#187; WSS 3.0 and MOSS 2007 Certification</dc:creator>
		<pubDate>Mon, 25 Aug 2008 18:53:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.importchaos.com/alonsorobles/?p=42#comment-379</guid>
		<description>[...] there are lots of good learning resources out there to help you prepare for the exams such as books, classes, and more. If you need helping preparing for an exam and finding classes or other learning [...]</description>
		<content:encoded><![CDATA[<p>[...] there are lots of good learning resources out there to help you prepare for the exams such as books, classes, and more. If you need helping preparing for an exam and finding classes or other learning [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Presenting at the Upcoming Los Angeles SharePoint User Group (LASPUG) Meeting - July 15, 2008 by Alonso Robles &#187; Blog Archive &#187; Introduction to the Enterprise Search Query Object Model</title>
		<link>http://blogs.importchaos.com/alonsorobles/2008/07/14/presenting-at-the-upcoming-los-angeles-sharepoint-user-group-laspug-meeting-july-15-2008/comment-page-1/#comment-359</link>
		<dc:creator>Alonso Robles &#187; Blog Archive &#187; Introduction to the Enterprise Search Query Object Model</dc:creator>
		<pubDate>Mon, 21 Jul 2008 23:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.importchaos.com/alonsorobles/?p=63#comment-359</guid>
		<description>[...] had the pleasure of delivering a presentation tonight at the monthly Los Angeles SharePoint User Group. The talk provided an introduction to the [...]</description>
		<content:encoded><![CDATA[<p>[...] had the pleasure of delivering a presentation tonight at the monthly Los Angeles SharePoint User Group. The talk provided an introduction to the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating Solution Packages for WSS 3.0 and MOSS 2007 Deployments by Alonso Robles / Caution When Packaging Themes for SharePoint Products and Technologies</title>
		<link>http://blogs.importchaos.com/alonsorobles/2008/05/16/creating-solution-packages-for-wss-30-and-moss-2007-deployments/comment-page-1/#comment-358</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-358</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>Comment on Packaging Branding and Themes for Deployment in SharePoint Environments by Alonso Robles / Caution When Packaging Themes for SharePoint Products and Technologies</title>
		<link>http://blogs.importchaos.com/alonsorobles/2008/06/26/packaging-branding-and-themes-for-deployment-in-sharepoint-environments/comment-page-1/#comment-356</link>
		<dc:creator>Alonso Robles / Caution When Packaging Themes for SharePoint Products and Technologies</dc:creator>
		<pubDate>Mon, 21 Jul 2008 18:50:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.importchaos.com/alonsorobles/?p=60#comment-356</guid>
		<description>[...] month, I wrote up a post about how to package themes in a WSS 3.0 Solution Package (WSP file) for deployment on a SharePoint farm. After playing with this package a bit there was on problem that I encountered that was pretty [...]</description>
		<content:encoded><![CDATA[<p>[...] month, I wrote up a post about how to package themes in a WSS 3.0 Solution Package (WSP file) for deployment on a SharePoint farm. After playing with this package a bit there was on problem that I encountered that was pretty [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating Solution Packages for WSS 3.0 and MOSS 2007 Deployments by Alonso Robles / Packaging Branding and Themes for Deployment in SharePoint Environments</title>
		<link>http://blogs.importchaos.com/alonsorobles/2008/05/16/creating-solution-packages-for-wss-30-and-moss-2007-deployments/comment-page-1/#comment-335</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-335</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>Comment on Creating a SharePoint Solution for an InfoPath Form Template Deployment by alonso.robles</title>
		<link>http://blogs.importchaos.com/alonsorobles/2008/06/04/creating-a-sharepoint-solution-for-an-infopath-form-template-deployment/comment-page-1/#comment-322</link>
		<dc:creator>alonso.robles</dc:creator>
		<pubDate>Fri, 20 Jun 2008 03:34:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.importchaos.com/alonsorobles/?p=50#comment-322</guid>
		<description>Jerry,

Yes, I think its possible. And you are right about needing two features (you can add many features to a single solution package). 

One thing to keep in mind is the deployment target of the workflow assembly. I am assuming Visual Studio created workflow with Windows Workflow Foundation. Workflow assemblies need to be deployed the GAC including the GAC of the application servers. So the solution deployment server type would need to be changed from a web front end to an application server. The application server option will push the assemblies to all of the servers.</description>
		<content:encoded><![CDATA[<p>Jerry,</p>
<p>Yes, I think its possible. And you are right about needing two features (you can add many features to a single solution package). </p>
<p>One thing to keep in mind is the deployment target of the workflow assembly. I am assuming Visual Studio created workflow with Windows Workflow Foundation. Workflow assemblies need to be deployed the GAC including the GAC of the application servers. So the solution deployment server type would need to be changed from a web front end to an application server. The application server option will push the assemblies to all of the servers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating a SharePoint Solution for an InfoPath Form Template Deployment by Jerry</title>
		<link>http://blogs.importchaos.com/alonsorobles/2008/06/04/creating-a-sharepoint-solution-for-an-infopath-form-template-deployment/comment-page-1/#comment-321</link>
		<dc:creator>Jerry</dc:creator>
		<pubDate>Fri, 20 Jun 2008 01:59:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.importchaos.com/alonsorobles/?p=50#comment-321</guid>
		<description>Cool!
I still have one more question, could the infopath form template solution be packaged with a workflow solution into one wsp file? Because these two kind of features have different ReceiverAssebly and ReceiverClass.</description>
		<content:encoded><![CDATA[<p>Cool!<br />
I still have one more question, could the infopath form template solution be packaged with a workflow solution into one wsp file? Because these two kind of features have different ReceiverAssebly and ReceiverClass.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 189 STSADM Operations by Alonso Robles / Creating a SharePoint Solution for an InfoPath Form Template Deployment</title>
		<link>http://blogs.importchaos.com/alonsorobles/2007/07/05/189-stsadm-operations/comment-page-1/#comment-279</link>
		<dc:creator>Alonso Robles / Creating a SharePoint Solution for an InfoPath Form Template Deployment</dc:creator>
		<pubDate>Thu, 05 Jun 2008 06:19:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.importchaos.com/alonsorobles/2007/07/05/189-stsadm-operations/#comment-279</guid>
		<description>[...] Quickly reviewing the commands above, we can see that we changed our working directory to the location of the publish path of the InfoPath form template (and the solution files). Then we generate the WSP file with the MAKECAP utility. Finally, using the STSADM utility we added the solution, deployed it, and activated the feature (for more information STSADM operations see my post on the 189 STSADM Operations).  [...]</description>
		<content:encoded><![CDATA[<p>[...] Quickly reviewing the commands above, we can see that we changed our working directory to the location of the publish path of the InfoPath form template (and the solution files). Then we generate the WSP file with the MAKECAP utility. Finally, using the STSADM utility we added the solution, deployed it, and activated the feature (for more information STSADM operations see my post on the 189 STSADM Operations).  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating Solution Packages for WSS 3.0 and MOSS 2007 Deployments by Alonso Robles / Creating a SharePoint Solution for an InfoPath Form Template Deployment</title>
		<link>http://blogs.importchaos.com/alonsorobles/2008/05/16/creating-solution-packages-for-wss-30-and-moss-2007-deployments/comment-page-1/#comment-278</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-278</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>
	<item>
		<title>Comment on SharePoint Ramp Up Webcasts for ASP.NET Developers by Alonso Robles / Setting up a SharePoint Development Environment to Support Silverlight Development</title>
		<link>http://blogs.importchaos.com/alonsorobles/2008/05/20/sharepoint-ramp-up-webcasts-for-aspnet-developers/comment-page-1/#comment-255</link>
		<dc:creator>Alonso Robles / Setting up a SharePoint Development Environment to Support Silverlight Development</dc:creator>
		<pubDate>Tue, 27 May 2008 17:37:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.importchaos.com/alonsorobles/?p=39#comment-255</guid>
		<description>[...] ASP.NET developers to Silverlight development for SharePoint. The webcast is the third in a series of webcasts to help ASP.NET developers get primed for SharePoint development. After the webcast Andrew was kind enough to post the steps he took in preparing his SharePoint [...]</description>
		<content:encoded><![CDATA[<p>[...] ASP.NET developers to Silverlight development for SharePoint. The webcast is the third in a series of webcasts to help ASP.NET developers get primed for SharePoint development. After the webcast Andrew was kind enough to post the steps he took in preparing his SharePoint [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
