<?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: Visual Studio 2008 Extensions for SharePoint (VSeWSS 1.3)</title>
	<atom:link href="http://artykul8.com/2009/08/visual-studio-2008-extensions-for-sharepoint/feed/" rel="self" type="application/rss+xml" />
	<link>http://artykul8.com/2009/08/visual-studio-2008-extensions-for-sharepoint/</link>
	<description>ar·tic·u·late (v.) to make clear or effective</description>
	<lastBuildDate>Fri, 03 Feb 2012 04:37:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: admin</title>
		<link>http://artykul8.com/2009/08/visual-studio-2008-extensions-for-sharepoint/comment-page-1/#comment-1730</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 04 Mar 2011 22:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://artykul8.com/?p=32#comment-1730</guid>
		<description>I find them both offering quite similar functionality. I personally enjoyed working with VSeWSS a bit more. The main difference though would be that VSeWSS is a product by Microsoft, while WSPBuilder is an open-source product. Generally you would expect a better support and integration provided by a professional organization. In addition, from consulting perspective if you look into larger deployments sometimes it is safer to stay with the official product, again mostly for the same support and maintainability reasons.</description>
		<content:encoded><![CDATA[<p>I find them both offering quite similar functionality. I personally enjoyed working with VSeWSS a bit more. The main difference though would be that VSeWSS is a product by Microsoft, while WSPBuilder is an open-source product. Generally you would expect a better support and integration provided by a professional organization. In addition, from consulting perspective if you look into larger deployments sometimes it is safer to stay with the official product, again mostly for the same support and maintainability reasons.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave</title>
		<link>http://artykul8.com/2009/08/visual-studio-2008-extensions-for-sharepoint/comment-page-1/#comment-1329</link>
		<dc:creator>dave</dc:creator>
		<pubDate>Fri, 11 Feb 2011 05:31:20 +0000</pubDate>
		<guid isPermaLink="false">http://artykul8.com/?p=32#comment-1329</guid>
		<description>Is Visual Studio Extensions similar to WSPBuilder? If so, which one is better? Thank you!</description>
		<content:encoded><![CDATA[<p>Is Visual Studio Extensions similar to WSPBuilder? If so, which one is better? Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter Trackbacks for Visual Studio 2008 Extensions for SharePoint (VSeWSS 1.3) &#124; artykul8 [artykul8.com] on Topsy.com</title>
		<link>http://artykul8.com/2009/08/visual-studio-2008-extensions-for-sharepoint/comment-page-1/#comment-7</link>
		<dc:creator>Twitter Trackbacks for Visual Studio 2008 Extensions for SharePoint (VSeWSS 1.3) &#124; artykul8 [artykul8.com] on Topsy.com</dc:creator>
		<pubDate>Thu, 20 Aug 2009 06:45:37 +0000</pubDate>
		<guid isPermaLink="false">http://artykul8.com/?p=32#comment-7</guid>
		<description>[...] Visual Studio 2008 Extensions for SharePoint (VSeWSS 1.3) &#124; artykul8  artykul8.com/2009/08/visual-studio-2008-extensions-for-sharepoint &#8211; cached page  Visual Studio 2008 Extensions for SharePoint (VSeWSS 1.3) still in beta/CTP phase &#8212; From the page [...]</description>
		<content:encoded><![CDATA[<p>[...] Visual Studio 2008 Extensions for SharePoint (VSeWSS 1.3) | artykul8  artykul8.com/2009/08/visual-studio-2008-extensions-for-sharepoint &ndash; cached page  Visual Studio 2008 Extensions for SharePoint (VSeWSS 1.3) still in beta/CTP phase &mdash; From the page [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

