<?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: IDEs considered harmful?</title>
	<atom:link href="http://www.owenpellegrin.com/blog/rants/ides-considered-harmful/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.owenpellegrin.com/blog/rants/ides-considered-harmful/</link>
	<description>I write stuff here</description>
	<lastBuildDate>Wed, 07 Jul 2010 09:26:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Sitten Spynne</title>
		<link>http://www.owenpellegrin.com/blog/rants/ides-considered-harmful/comment-page-1/#comment-500</link>
		<dc:creator>Sitten Spynne</dc:creator>
		<pubDate>Wed, 25 Jun 2008 15:50:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.atmaweapon.org/blog/?p=23#comment-500</guid>
		<description>I&#039;d love to respond via email... except your blog link is incorrect and when I did find your blog there&#039;s no contact information.

FYI, in case you see it, the root element in these loose XAML files is typically Window; sometimes I just want a UI playground with no code-behind.  In particular, this made following along with Charles Petzold&#039;s WPF book annoying, because the only alternative to VS was XAMLPad or his XAML Cruncher, neither of which has intelligent tabbing, Intellisense, etc.

It&#039;s not necessarily a failure to address a super-common use case, but it is a good example of how the limitations of the tool you use can affect how you approach problems.  A user unfamiliar with WPF might draw the conclusion that you cannot have a WPF window with &lt;i&gt;just&lt;/i&gt; a code file or &lt;i&gt;just&lt;/i&gt; a XAML file.</description>
		<content:encoded><![CDATA[<p>I&#8217;d love to respond via email&#8230; except your blog link is incorrect and when I did find your blog there&#8217;s no contact information.</p>
<p>FYI, in case you see it, the root element in these loose XAML files is typically Window; sometimes I just want a UI playground with no code-behind.  In particular, this made following along with Charles Petzold&#8217;s WPF book annoying, because the only alternative to VS was XAMLPad or his XAML Cruncher, neither of which has intelligent tabbing, Intellisense, etc.</p>
<p>It&#8217;s not necessarily a failure to address a super-common use case, but it is a good example of how the limitations of the tool you use can affect how you approach problems.  A user unfamiliar with WPF might draw the conclusion that you cannot have a WPF window with <i>just</i> a code file or <i>just</i> a XAML file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Relyea</title>
		<link>http://www.owenpellegrin.com/blog/rants/ides-considered-harmful/comment-page-1/#comment-498</link>
		<dc:creator>Rob Relyea</dc:creator>
		<pubDate>Tue, 24 Jun 2008 18:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.atmaweapon.org/blog/?p=23#comment-498</guid>
		<description>The ResourceDictionary item is another option...but again, not a great one.

What root element are you usually putting in your loose xaml file?
(please reply via email and point me towards this post...so i remember the context.)

Thanks, Rob Relyea
WPF Team</description>
		<content:encoded><![CDATA[<p>The ResourceDictionary item is another option&#8230;but again, not a great one.</p>
<p>What root element are you usually putting in your loose xaml file?<br />
(please reply via email and point me towards this post&#8230;so i remember the context.)</p>
<p>Thanks, Rob Relyea<br />
WPF Team</p>
]]></content:encoded>
	</item>
</channel>
</rss>
