<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>out &#62;&#62; m_Conscientia; &#187; team system</title>
	<atom:link href="http://blog.hypercomplex.co.uk/index.php/tag/team-system/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hypercomplex.co.uk</link>
	<description>a multidimensional braindump</description>
	<lastBuildDate>Sat, 27 Aug 2011 19:16:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Code Coverage in VSTS 2005</title>
		<link>http://blog.hypercomplex.co.uk/index.php/2009/02/code-coverage-in-vsts-2005/</link>
		<comments>http://blog.hypercomplex.co.uk/index.php/2009/02/code-coverage-in-vsts-2005/#comments</comments>
		<pubDate>Fri, 06 Feb 2009 15:30:46 +0000</pubDate>
		<dc:creator>Alex Peck</dc:creator>
				<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[code coverage]]></category>
		<category><![CDATA[team system]]></category>
		<category><![CDATA[visual studio]]></category>

		<guid isPermaLink="false">http://www.blog.hypercomplex.co.uk/?p=5</guid>
		<description><![CDATA[I&#8217;m measuring test code coverage on an application stack with both .NET (managed) and native (unmanaged) components. For some reason the help doesn&#8217;t explicitly state how this is accomplished, and some googling suggested that you need to go outside the IDE to instrument the native code. This isn&#8217;t the case. With a Visual Studio 2005 [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m measuring test code coverage on an application stack with both .NET (managed) and native (unmanaged) components. For some reason the help doesn&#8217;t explicitly state how this is accomplished, and some googling suggested that you need to go outside the IDE to instrument the native code.</p>
<p>This isn&#8217;t the case. With a Visual Studio 2005 solution consisting of:</p>
<ul>
<li>a native .dll project</li>
<li>a .NET .dll project</li>
<li>an mstest project</li>
</ul>
<p>Instrumentation can be enabled by editing the localtestrun.testrunconfig solution item. Look for the code coverage section and select the artifacts you want to instrument. <strong></strong></p>
<p><strong>Caveat</strong>: the native binary will not be instrumented unless it is linked with the /PROFILE switch. There is no error message if you forget, it just silently fails to collect coverage for the .dll.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.hypercomplex.co.uk/index.php/2009/02/code-coverage-in-vsts-2005/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

