<?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: Make Code Coverage in Navision (NAV) a Little More Useful</title>
	<atom:link href="http://www.BillWarnke.com/2008/12/make-code-coverage-in-nav-a-little-more-useful/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.BillWarnke.com/2008/12/make-code-coverage-in-nav-a-little-more-useful/</link>
	<description>4C657420546865726520426520526F636B2E00</description>
	<lastBuildDate>Thu, 08 Jul 2010 08:22:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: alexandersen</title>
		<link>http://www.BillWarnke.com/2008/12/make-code-coverage-in-nav-a-little-more-useful/comment-page-1/#comment-22</link>
		<dc:creator>alexandersen</dc:creator>
		<pubDate>Wed, 21 Oct 2009 23:52:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.billwarnke.com/?p=128#comment-22</guid>
		<description>Hi!&lt;br&gt;Exactly.. that is a great feature.. being able to filter, so only the lines of code that are &quot;hit&quot; are visible.&lt;br&gt;&lt;br&gt;Furthermore, you can set a parameter in the users shortcut, that enables logging of code to the named file, whenever Code Coverage is used in the session. This means that you can log specific areas by enabling and disabling the Code Coverage via code. Resulting in a Code Coverage file, that the user can then send to a NAV support for inspection. Great feature!</description>
		<content:encoded><![CDATA[<p>Hi!<br />Exactly.. that is a great feature.. being able to filter, so only the lines of code that are &#8220;hit&#8221; are visible.</p>
<p>Furthermore, you can set a parameter in the users shortcut, that enables logging of code to the named file, whenever Code Coverage is used in the session. This means that you can log specific areas by enabling and disabling the Code Coverage via code. Resulting in a Code Coverage file, that the user can then send to a NAV support for inspection. Great feature!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alexandersen</title>
		<link>http://www.BillWarnke.com/2008/12/make-code-coverage-in-nav-a-little-more-useful/comment-page-1/#comment-16</link>
		<dc:creator>alexandersen</dc:creator>
		<pubDate>Wed, 21 Oct 2009 17:52:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.billwarnke.com/?p=128#comment-16</guid>
		<description>Hi!&lt;br&gt;Exactly.. that is a great feature.. being able to filter, so only the lines of code that are &quot;hit&quot; are visible.&lt;br&gt;&lt;br&gt;Furthermore, you can set a parameter in the users shortcut, that enables logging of code to the named file, whenever Code Coverage is used in the session. This means that you can log specific areas by enabling and disabling the Code Coverage via code. Resulting in a Code Coverage file, that the user can then send to a NAV support for inspection. Great feature!</description>
		<content:encoded><![CDATA[<p>Hi!<br />Exactly.. that is a great feature.. being able to filter, so only the lines of code that are &#8220;hit&#8221; are visible.</p>
<p>Furthermore, you can set a parameter in the users shortcut, that enables logging of code to the named file, whenever Code Coverage is used in the session. This means that you can log specific areas by enabling and disabling the Code Coverage via code. Resulting in a Code Coverage file, that the user can then send to a NAV support for inspection. Great feature!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
