<?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: Building a SharePoint 2007/2010 development environment &#8211; Part II: Design</title>
	<atom:link href="http://tristanwatkins.com/building-a-sharepoint-20072010-development-environment-part-ii-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://tristanwatkins.com/building-a-sharepoint-20072010-development-environment-part-ii-design/</link>
	<description>Technical guidance for SharePoint, Cloud Services, Windows and more</description>
	<lastBuildDate>Tue, 21 May 2013 03:21:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Publishing a network-isolated virtual machine with RemoteApp &#171; Tristan Watkins</title>
		<link>http://tristanwatkins.com/building-a-sharepoint-20072010-development-environment-part-ii-design/#comment-79</link>
		<dc:creator>Publishing a network-isolated virtual machine with RemoteApp &#171; Tristan Watkins</dc:creator>
		<pubDate>Wed, 21 Apr 2010 06:40:09 +0000</pubDate>
		<guid isPermaLink="false">http://tristanwatkins.com/?p=499#comment-79</guid>
		<description><![CDATA[[...] development environment design choices that this article pertains to, it may be worth glancing at the design section of my SharePoint development series before diving in, if you haven&#039;t already followed those [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] development environment design choices that this article pertains to, it may be worth glancing at the design section of my SharePoint development series before diving in, if you haven&#39;t already followed those [...] </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SharePoint 2010 (not) in a Workgroup &#171; Tristan Watkins</title>
		<link>http://tristanwatkins.com/building-a-sharepoint-20072010-development-environment-part-ii-design/#comment-78</link>
		<dc:creator>SharePoint 2010 (not) in a Workgroup &#171; Tristan Watkins</dc:creator>
		<pubDate>Mon, 29 Mar 2010 23:08:29 +0000</pubDate>
		<guid isPermaLink="false">http://tristanwatkins.com/?p=499#comment-78</guid>
		<description><![CDATA[[...] for many of the reasons that I chose to do so in 2007 (see the Workgroup Development section in Part II of my series on SharePoint development environments). Now, the SharePoint 2010 Configuration Wizard (psconfigui) throws an error when choosing the [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] for many of the reasons that I chose to do so in 2007 (see the Workgroup Development section in Part II of my series on SharePoint development environments). Now, the SharePoint 2010 Configuration Wizard (psconfigui) throws an error when choosing the [...] </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NewSID myth implications for SharePoint development &#171; Archimatic Infostructure</title>
		<link>http://tristanwatkins.com/building-a-sharepoint-20072010-development-environment-part-ii-design/#comment-77</link>
		<dc:creator>NewSID myth implications for SharePoint development &#171; Archimatic Infostructure</dc:creator>
		<pubDate>Wed, 11 Nov 2009 00:04:31 +0000</pubDate>
		<guid isPermaLink="false">http://tristanwatkins.com/?p=499#comment-77</guid>
		<description><![CDATA[[...] replica without any reconfiguration. This is a preference and I think there are big benefits to it, as I&#039;ve explained, but there are many ways to approach this, and to speak to the NewSID questions, all are equally [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] replica without any reconfiguration. This is a preference and I think there are big benefits to it, as I&#39;ve explained, but there are many ways to approach this, and to speak to the NewSID questions, all are equally [...] </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Building a SharePoint 2007/2010 development environment &#8211; Part III: Host image build and performance benchmarks &#171; Archimatic Infostructure</title>
		<link>http://tristanwatkins.com/building-a-sharepoint-20072010-development-environment-part-ii-design/#comment-76</link>
		<dc:creator>Building a SharePoint 2007/2010 development environment &#8211; Part III: Host image build and performance benchmarks &#171; Archimatic Infostructure</dc:creator>
		<pubDate>Fri, 06 Nov 2009 00:29:52 +0000</pubDate>
		<guid isPermaLink="false">http://tristanwatkins.com/?p=499#comment-76</guid>
		<description><![CDATA[[...] agreed the project objectives and designed the system, I turned my attention to the Hyper-V host image build. This is a high-level build guide with [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] agreed the project objectives and designed the system, I turned my attention to the Hyper-V host image build. This is a high-level build guide with [...] </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Building a SharePoint 2007/2010 development environment &#8211; Part I: Introduction and Objectives &#171; Archimatic Infostructure</title>
		<link>http://tristanwatkins.com/building-a-sharepoint-20072010-development-environment-part-ii-design/#comment-75</link>
		<dc:creator>Building a SharePoint 2007/2010 development environment &#8211; Part I: Introduction and Objectives &#171; Archimatic Infostructure</dc:creator>
		<pubDate>Thu, 05 Nov 2009 01:45:59 +0000</pubDate>
		<guid isPermaLink="false">http://tristanwatkins.com/?p=499#comment-75</guid>
		<description><![CDATA[[...] we hoped to achieve with the new approach. The design decisions will be covered in more detail in the second post, followed by a deeper look at detailed build [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] we hoped to achieve with the new approach. The design decisions will be covered in more detail in the second post, followed by a deeper look at detailed build [...] </p>
]]></content:encoded>
	</item>
</channel>
</rss>
