<?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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Using third party tools in SharePoint</title>
	<atom:link href="http://sharepointmagazine.net/news/using-third-party-tools-in-sharepoint/feed" rel="self" type="application/rss+xml" />
	<link>http://sharepointmagazine.net/news/using-third-party-tools-in-sharepoint</link>
	<description>SharePoint Magazine is an online Magazine dedicated to the world of SharePoint</description>
	<lastBuildDate>Thu, 11 Mar 2010 21:38:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: whymoore</title>
		<link>http://sharepointmagazine.net/news/using-third-party-tools-in-sharepoint/comment-page-1#comment-797</link>
		<dc:creator>whymoore</dc:creator>
		<pubDate>Tue, 07 Apr 2009 01:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=2398#comment-797</guid>
		<description>I agree, a serious attempt at performing QA on SharePoint products needs to not only to examine the basic differences between WSS and MOSS, but needs also to take a serious look at the customizability and extensibility of SharePoint. Load balanced and multi-server environments are becoming standard enough that most ISVs / 3rd Party Vendors are familiar with the challenges there. But custom workflows, web parts, features, and solutions are certainly starting to take off as both in-house and consultant-based developments. The need here does not necessarily fall to the vendors of this code but to Microsoft itself. SharePoint 14 and Visual Studios 10 must make sure that the open ended and flexible deployment of solutions and features follows a regular and recognizable pattern for QA developers to do their job well. &lt;br&gt;&lt;br&gt;I’ll add to your list above that when considering a 3rd party vendor, make sure that they’re a Microsoft Managed partner or Gold Certified Partner, and that they’re involved in the TAP program to plan ahead for compatibility and differences in future versions, not just the current one. A good example is &lt;a href=&quot;http://www.avepoint.com&quot; rel=&quot;nofollow&quot;&gt;www.avepoint.com&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>I agree, a serious attempt at performing QA on SharePoint products needs to not only to examine the basic differences between WSS and MOSS, but needs also to take a serious look at the customizability and extensibility of SharePoint. Load balanced and multi-server environments are becoming standard enough that most ISVs / 3rd Party Vendors are familiar with the challenges there. But custom workflows, web parts, features, and solutions are certainly starting to take off as both in-house and consultant-based developments. The need here does not necessarily fall to the vendors of this code but to Microsoft itself. SharePoint 14 and Visual Studios 10 must make sure that the open ended and flexible deployment of solutions and features follows a regular and recognizable pattern for QA developers to do their job well. </p>
<p>I’ll add to your list above that when considering a 3rd party vendor, make sure that they’re a Microsoft Managed partner or Gold Certified Partner, and that they’re involved in the TAP program to plan ahead for compatibility and differences in future versions, not just the current one. A good example is <a href="http://www.avepoint.com" rel="nofollow">http://www.avepoint.com</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick McDannel</title>
		<link>http://sharepointmagazine.net/news/using-third-party-tools-in-sharepoint/comment-page-1#comment-786</link>
		<dc:creator>Rick McDannel</dc:creator>
		<pubDate>Tue, 24 Mar 2009 03:32:53 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=2398#comment-786</guid>
		<description>Nice article.  We discovered some of the same &quot;gotchas&quot; with third-party tools.  Your points are valid and should be considered before evaluating add-ons.  For instance, one product we looked at had all of the functionality we needed, but it broke the native content deployment or STSADM backup/restore functionality.  Spent many hours fighting this.</description>
		<content:encoded><![CDATA[<p>Nice article.  We discovered some of the same &#8220;gotchas&#8221; with third-party tools.  Your points are valid and should be considered before evaluating add-ons.  For instance, one product we looked at had all of the functionality we needed, but it broke the native content deployment or STSADM backup/restore functionality.  Spent many hours fighting this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: loumf</title>
		<link>http://sharepointmagazine.net/news/using-third-party-tools-in-sharepoint/comment-page-1#comment-768</link>
		<dc:creator>loumf</dc:creator>
		<pubDate>Sat, 21 Mar 2009 01:13:42 +0000</pubDate>
		<guid isPermaLink="false">http://sharepointmagazine.net/?p=2398#comment-768</guid>
		<description>Great article -- very comprehensive.  I can&#039;t begin to address all of these questions, but I blogged here:&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.atalasoft.com/cs/blogs/loufranco/archive/2009/03/20/great-advice-from-sharepoint-magazine-on-third-party-add-ons.aspx&quot; rel=&quot;nofollow&quot;&gt;http://www.atalasoft.com/cs/blogs/loufranco/arc...&lt;/a&gt;&lt;br&gt;&lt;br&gt;About how Atalasoft addresses some of these questions with Vizit. I think this article is a must-read (and must address) one for anybody hoping to sell third-party addons to SharePoint.</description>
		<content:encoded><![CDATA[<p>Great article &#8212; very comprehensive.  I can&#39;t begin to address all of these questions, but I blogged here:</p>
<p><a href="http://www.atalasoft.com/cs/blogs/loufranco/archive/2009/03/20/great-advice-from-sharepoint-magazine-on-third-party-add-ons.aspx" rel="nofollow"></a><a href="http://www.atalasoft.com/cs/blogs/loufranco/arc.." rel="nofollow">http://www.atalasoft.com/cs/blogs/loufranco/arc..</a>.</p>
<p>About how Atalasoft addresses some of these questions with Vizit. I think this article is a must-read (and must address) one for anybody hoping to sell third-party addons to SharePoint.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
