<?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"
	>
<channel>
	<title>Comments for Professional Visual Studio</title>
	<atom:link href="http://www.professionalvisualstudio.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.professionalvisualstudio.com/blog</link>
	<description>Tips, Tricks, and Best Practices for professional .NET developers</description>
	<pubDate>Thu, 21 Aug 2008 18:41:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>Comment on Hiding the Output Window by Visual Studio Links #67 : Visual Studio Hacks</title>
		<link>http://www.professionalvisualstudio.com/blog/2008/08/19/hiding-the-output-window/#comment-163</link>
		<dc:creator>Visual Studio Links #67 : Visual Studio Hacks</dc:creator>
		<pubDate>Thu, 21 Aug 2008 14:39:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.professionalvisualstudio.com/blog/?p=116#comment-163</guid>
		<description>[...] Gardner posted a tip on Hiding the Output Window for builds. Technorati Tags: [...]</description>
		<content:encoded><![CDATA[<p>[...] Gardner posted a tip on Hiding the Output Window for builds. Technorati Tags: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Debugging Tip of the Week #1: The Immediate Window by Professional Visual Studio &#187; Hiding the Output Window</title>
		<link>http://www.professionalvisualstudio.com/blog/2008/07/24/debugging-tip-of-the-week-1-the-immediate-window/#comment-161</link>
		<dc:creator>Professional Visual Studio &#187; Hiding the Output Window</dc:creator>
		<pubDate>Tue, 19 Aug 2008 12:41:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.professionalvisualstudio.com/blog/2008/07/24/debugging-tip-of-the-week-1-the-immediate-window/#comment-161</guid>
		<description>[...] can redirect all Diagnostic messages (e.g. Debug.Print) to the Immediate Window, as mentioned in my first Debugging Tip of the Week.       [...]</description>
		<content:encoded><![CDATA[<p>[...] can redirect all Diagnostic messages (e.g. Debug.Print) to the Immediate Window, as mentioned in my first Debugging Tip of the Week.       [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Debugging Tip of the Week #4: The DebuggerDisplay Attribute by Visual Studio Links #66 : Visual Studio Hacks</title>
		<link>http://www.professionalvisualstudio.com/blog/2008/08/15/debugging-tip-of-the-week-4-the-debuggerdisplay-attribute/#comment-160</link>
		<dc:creator>Visual Studio Links #66 : Visual Studio Hacks</dc:creator>
		<pubDate>Mon, 18 Aug 2008 11:56:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.professionalvisualstudio.com/blog/?p=125#comment-160</guid>
		<description>[...] Dave Gardner posted the latest debugging tip of the week - The DebuggerDisplay Attribute. [...]</description>
		<content:encoded><![CDATA[<p>[...] Dave Gardner posted the latest debugging tip of the week - The DebuggerDisplay Attribute. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Debugging Tip of the Week #3: The DebuggerBrowsable Attribute by Professional Visual Studio &#187; Debugging Tip of the Week #4: The DebuggerDisplay Attribute</title>
		<link>http://www.professionalvisualstudio.com/blog/2008/08/07/debugging-tip-of-the-week-3-the-debuggerbrowsable-attribute/#comment-159</link>
		<dc:creator>Professional Visual Studio &#187; Debugging Tip of the Week #4: The DebuggerDisplay Attribute</dc:creator>
		<pubDate>Fri, 15 Aug 2008 11:50:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.professionalvisualstudio.com/blog/2008/08/07/debugging-tip-of-the-week-3-the-debuggerbrowsable-attribute/#comment-159</guid>
		<description>[...] first of the Debugger attributes that are found in the System.Diagnostics namespace by looking at the DebuggerBrowsable attribute. I&#8217;d like to continue that theme this week with the DebuggerDisplay [...]</description>
		<content:encoded><![CDATA[<p>[...] first of the Debugger attributes that are found in the System.Diagnostics namespace by looking at the DebuggerBrowsable attribute. I&#8217;d like to continue that theme this week with the DebuggerDisplay [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Professional Visual Studio 2008 is now available by Dave Gardner</title>
		<link>http://www.professionalvisualstudio.com/blog/2008/07/28/professional-visual-studio-2008-is-now-available/#comment-158</link>
		<dc:creator>Dave Gardner</dc:creator>
		<pubDate>Thu, 14 Aug 2008 07:46:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.professionalvisualstudio.com/blog/2008/07/28/professional-visual-studio-2008-is-now-available/#comment-158</guid>
		<description>I think you will find our book to be ideal. In addition to covering Visual Studio 2008 itself, we also provide an introduction of many of the new language features and .NET Framework 3.0/3.5 functionality, such as LINQ, WPF, WCF, WF, etc. While we obviously can't go into enough depth to make you an expert in these topics, we cover the fundamentals of them pretty well and certainly give you enough information to get a project up and running with these technologies.

I've had the same frustrations with taking courses, and have more than once felt that the instructor didn't know the topic very well at all. The only really useful thing about taking a course is that it forces you to spend the time learning about the topic. However with a book you can skip over the introductory chapters on the basics of Visual Studio, and spend your time reading the chapters that cover the topics you are most interested in.</description>
		<content:encoded><![CDATA[<p>I think you will find our book to be ideal. In addition to covering Visual Studio 2008 itself, we also provide an introduction of many of the new language features and .NET Framework 3.0/3.5 functionality, such as LINQ, WPF, WCF, WF, etc. While we obviously can&#8217;t go into enough depth to make you an expert in these topics, we cover the fundamentals of them pretty well and certainly give you enough information to get a project up and running with these technologies.</p>
<p>I&#8217;ve had the same frustrations with taking courses, and have more than once felt that the instructor didn&#8217;t know the topic very well at all. The only really useful thing about taking a course is that it forces you to spend the time learning about the topic. However with a book you can skip over the introductory chapters on the basics of Visual Studio, and spend your time reading the chapters that cover the topics you are most interested in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Professional Visual Studio 2008 is now available by Ali</title>
		<link>http://www.professionalvisualstudio.com/blog/2008/07/28/professional-visual-studio-2008-is-now-available/#comment-157</link>
		<dc:creator>Ali</dc:creator>
		<pubDate>Wed, 13 Aug 2008 03:26:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.professionalvisualstudio.com/blog/2008/07/28/professional-visual-studio-2008-is-now-available/#comment-157</guid>
		<description>I have good experience working with VS 2003 &#38; 2005. I haven't worked yet with VS 2008, will this book be enough for me instead of taking a course, which tend to be basic &#38; useless most of the time.</description>
		<content:encoded><![CDATA[<p>I have good experience working with VS 2003 &amp; 2005. I haven&#8217;t worked yet with VS 2008, will this book be enough for me instead of taking a course, which tend to be basic &amp; useless most of the time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Debugging Tip of the Week #3: The DebuggerBrowsable Attribute by Visual Studio Links #63 : Visual Studio Hacks</title>
		<link>http://www.professionalvisualstudio.com/blog/2008/08/07/debugging-tip-of-the-week-3-the-debuggerbrowsable-attribute/#comment-156</link>
		<dc:creator>Visual Studio Links #63 : Visual Studio Hacks</dc:creator>
		<pubDate>Mon, 11 Aug 2008 12:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.professionalvisualstudio.com/blog/2008/08/07/debugging-tip-of-the-week-3-the-debuggerbrowsable-attribute/#comment-156</guid>
		<description>[...] Dave Gardner continues his tip series with Debugging Tip of the Week #3:&#160; The DebuggerBrowsable Attribute. [...]</description>
		<content:encoded><![CDATA[<p>[...] Dave Gardner continues his tip series with Debugging Tip of the Week #3:&nbsp; The DebuggerBrowsable Attribute. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Debugging Tip of the Week #2: Design-time Expression Evaluation by Visual Studio Links #59 : Visual Studio Hacks</title>
		<link>http://www.professionalvisualstudio.com/blog/2008/07/31/debugging-tip-of-the-week-2-design-time-expression-evaluation/#comment-153</link>
		<dc:creator>Visual Studio Links #59 : Visual Studio Hacks</dc:creator>
		<pubDate>Fri, 01 Aug 2008 21:54:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.professionalvisualstudio.com/blog/2008/07/31/debugging-tip-of-the-week-2-design-time-expression-evaluation/#comment-153</guid>
		<description>[...] Dave Gardner's Debugging Tip of the Week #2 covers Design-time Expression Evaluation. [...]</description>
		<content:encoded><![CDATA[<p>[...] Dave Gardner&#8217;s Debugging Tip of the Week #2 covers Design-time Expression Evaluation. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Is a class diagram worth 1000 lines of code? by Sam Burns</title>
		<link>http://www.professionalvisualstudio.com/blog/2008/02/08/is-a-class-diagram-worth-1000-lines-of-code/#comment-152</link>
		<dc:creator>Sam Burns</dc:creator>
		<pubDate>Fri, 01 Aug 2008 16:22:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.professionalvisualstudio.com/blog/2008/02/08/is-a-class-diagram-worth-1000-lines-of-code/#comment-152</guid>
		<description>The article was very useful to me for the link to the power toys designer.  I was hoping it would fix an issue I have with Visual Studio 2005 where selecting Layout Diagram causes lots of classes to collapse even after you specifically expanded them all.</description>
		<content:encoded><![CDATA[<p>The article was very useful to me for the link to the power toys designer.  I was hoping it would fix an issue I have with Visual Studio 2005 where selecting Layout Diagram causes lots of classes to collapse even after you specifically expanded them all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Debugging Tip of the Week #1: The Immediate Window by Professional Visual Studio &#187; Debugging Tip of the Week #2: Design-time Expression Evaluation</title>
		<link>http://www.professionalvisualstudio.com/blog/2008/07/24/debugging-tip-of-the-week-1-the-immediate-window/#comment-151</link>
		<dc:creator>Professional Visual Studio &#187; Debugging Tip of the Week #2: Design-time Expression Evaluation</dc:creator>
		<pubDate>Thu, 31 Jul 2008 12:43:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.professionalvisualstudio.com/blog/2008/07/24/debugging-tip-of-the-week-1-the-immediate-window/#comment-151</guid>
		<description>[...] week I talked about how useful the Immediate Window is during debug-mode. A less-known, but totally awesome, feature of the Immediate Window is that it can be used at [...]</description>
		<content:encoded><![CDATA[<p>[...] week I talked about how useful the Immediate Window is during debug-mode. A less-known, but totally awesome, feature of the Immediate Window is that it can be used at [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
