<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>NUnitLite Work Item Rss Feed</title><link>http://www.codeplex.com/WorkItem/List.aspx?ProjectName=NUnitLite</link><description>NUnitLite Work Item Rss Description</description><item><title>CLOSED ISSUE: Need projects for compact framework</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12447</link><description>It would be convenient to have NUnitLite and NUnitLiteTests projects for compact framework so that people don&amp;#39;t have to create them and copy the files themselves. We may want separate sets for .NET CF 1.0 and 2.0 as well.&lt;br /&gt;Comments: Included in release 0.2.0</description><author>cpoole</author><pubDate>Sun, 04 Nov 2007 01:00:14 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: Need projects for compact framework 20071104010014A</guid></item><item><title>CLOSED TASK: Generalize "Console" Output</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12449</link><description>Not all platforms have a console device. And in .NET CF 1.0, the console output can not be redirected.&lt;br /&gt;&lt;br /&gt;Therefore... we should do all our text output to a TextWriter interace and inject the appropriate object based on the platform and possibly as user options. One implementation could output to the Console, another to a file, another to Debug, etc. We can even output to a window on the device if we want.&lt;br /&gt;&lt;br /&gt;NOTE&amp;#58; This is not a substitute for XML output, just a way to handle text output where we have it&lt;br /&gt;Comments: In 0.2.0 release</description><author>cpoole</author><pubDate>Sun, 04 Nov 2007 00:57:45 GMT</pubDate><guid isPermaLink="false">CLOSED TASK: Generalize "Console" Output 20071104125745A</guid></item><item><title>CLOSED TASK: ExpectedException not Handled on Compact Framework</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12446</link><description>On CF all tests with Expected Exceptions are simply reporting the excetpion rather than handling it.&lt;br /&gt;&lt;br /&gt;This appears to be due to one of several places where we catch a TargetInvocationException. expecting its Inner exception to be the actual exception. This works on desktop .NET but on CF the basic exception is thrown without wrapping it in a TargetInvocationException.&lt;br /&gt;&lt;br /&gt;While fixing this, all catch blocks should be analyzed to make sure that they don&amp;#39;t need a catch&amp;#40;Exception&amp;#41; as the last catch.&lt;br /&gt;Comments: In 0.2.0 release</description><author>cpoole</author><pubDate>Sun, 04 Nov 2007 00:56:12 GMT</pubDate><guid isPermaLink="false">CLOSED TASK: ExpectedException not Handled on Compact Framework 20071104125612A</guid></item><item><title>CLOSED TASK: Incorrect preprocessor constant used in DisplayHelp()</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12361</link><description>At line 132 of CommandLineOptions.cs &amp;#40;the DisplayHelp&amp;#40;&amp;#41; method&amp;#41;, there is a preprocessor conditional block which uses the define WindowsCD. This should be WindowsCE.&lt;br /&gt;Comments: In 0.2.0 release</description><author>cpoole</author><pubDate>Sun, 04 Nov 2007 00:55:04 GMT</pubDate><guid isPermaLink="false">CLOSED TASK: Incorrect preprocessor constant used in DisplayHelp() 20071104125504A</guid></item><item><title>CLOSED ISSUE: StackFilter still uses NUnitLite namespace</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12372</link><description>The StackFilter class looks for NUnitLite.Framework classes to eliminate from the stack even though we changed the namespace to be NUnit.Framework. The tests are also incorrect.&lt;br /&gt;&lt;br /&gt;In addition, the filter is currently removing classes in the middle of the call stack rather than just at the top as it should. We need more tests to confirm and fix this.&lt;br /&gt;Comments: Included i 0.2.0 release</description><author>cpoole</author><pubDate>Sun, 04 Nov 2007 00:53:35 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: StackFilter still uses NUnitLite namespace 20071104125335A</guid></item><item><title>CLOSED TASK: NUnitLite.sln still contains a reference to CppTests\CppTests.vcproj</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12410</link><description>see corresponding email&lt;br /&gt;Comments: Fixed in source</description><author>cpoole</author><pubDate>Sun, 28 Oct 2007 16:02:20 GMT</pubDate><guid isPermaLink="false">CLOSED TASK: NUnitLite.sln still contains a reference to CppTests\CppTests.vcproj 20071028040220P</guid></item><item><title>CLOSED ISSUE: update copyright info in copyright information in NUnitLiteTests\Properties\AssemblyInfo.cs</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12412</link><description>is 2006, should be 2007&lt;br/&gt;</description><author>cpoole</author><pubDate>Sun, 26 Aug 2007 03:06:29 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: update copyright info in copyright information in NUnitLiteTests\Properties\AssemblyInfo.cs 20070826030629A</guid></item><item><title>CREATED ISSUE: Generalize "Console" Output</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12449</link><description>Not all platforms have a console device. And in .NET CF 1.0, the console output can not be redirected.&lt;br /&gt;&lt;br /&gt;Therefore... we should do all our text output to a TextWriter interace and inject the appropriate object based on the platform and possibly as user options. One implementation could output to the Console, another to a file, another to Debug, etc. We can even output to a window on the device if we want.&lt;br /&gt;&lt;br /&gt;NOTE&amp;#58; This is not a substitute for XML output, just a way to handle text output where we have it&lt;br/&gt;</description><author>cpoole</author><pubDate>Sat, 25 Aug 2007 22:35:12 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Generalize "Console" Output 20070825103512P</guid></item><item><title>CREATED ISSUE: Add the .NET micro framework as a supporte platform</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12448</link><description>... and make it work, of course&amp;#33;&lt;br/&gt;</description><author>cpoole</author><pubDate>Sat, 25 Aug 2007 22:29:25 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Add the .NET micro framework as a supporte platform 20070825102925P</guid></item><item><title>CREATED ISSUE: Need projects for compact framework</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12447</link><description>It would be convenient to have NUnitLite and NUnitLiteTests projects for compact framework so that people don&amp;#39;t have to create them and copy the files themselves. We may want separate sets for .NET CF 1.0 and 2.0 as well.&lt;br/&gt;</description><author>cpoole</author><pubDate>Sat, 25 Aug 2007 22:27:01 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Need projects for compact framework 20070825102701P</guid></item><item><title>CREATED TASK: ExpectedException not Handled on Compact Framework</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12446</link><description>On CF all tests with Expected Exceptions are simply reporting the excetpion rather than handling it.&lt;br /&gt;&lt;br /&gt;This appears to be due to one of several places where we catch a TargetInvocationException. expecting its Inner exception to be the actual exception. This works on desktop .NET but on CF the basic exception is thrown without wrapping it in a TargetInvocationException.&lt;br /&gt;&lt;br /&gt;While fixing this, all catch blocks should be analyzed to make sure that they don&amp;#39;t need a catch&amp;#40;Exception&amp;#41; as the last catch.&lt;br/&gt;</description><author>cpoole</author><pubDate>Sat, 25 Aug 2007 22:12:18 GMT</pubDate><guid isPermaLink="false">CREATED TASK: ExpectedException not Handled on Compact Framework 20070825101218P</guid></item><item><title>CLOSED ISSUE: typo in src\NUnitLite\Runner\CommandLineOptions.cs, line 132</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12411</link><description>src&amp;#92;NUnitLite&amp;#92;Runner&amp;#92;CommandLineOptions.cs, line 132 reads&lt;br /&gt;    &amp;#35;if PocketPC &amp;#124;&amp;#124; WindowsCD &amp;#124;&amp;#124; NETCF&lt;br /&gt;but should probably be&lt;br /&gt;    &amp;#35;if PocketPC &amp;#124;&amp;#124; WindowsCE &amp;#124;&amp;#124; NETCF&lt;br/&gt;Comments: Duplicate of #`12361, fixed in source</description><author>cpoole</author><pubDate>Fri, 24 Aug 2007 05:40:07 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: typo in src\NUnitLite\Runner\CommandLineOptions.cs, line 132 20070824054007A</guid></item><item><title>COMMENTED ISSUE: typo in src\NUnitLite\Runner\CommandLineOptions.cs, line 132</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12411</link><description>src&amp;#92;NUnitLite&amp;#92;Runner&amp;#92;CommandLineOptions.cs, line 132 reads&lt;br /&gt;    &amp;#35;if PocketPC &amp;#124;&amp;#124; WindowsCD &amp;#124;&amp;#124; NETCF&lt;br /&gt;but should probably be&lt;br /&gt;    &amp;#35;if PocketPC &amp;#124;&amp;#124; WindowsCE &amp;#124;&amp;#124; NETCF&lt;br/&gt;Comments: ** Comment from web user: cpoole ** &lt;p&gt;Duplicate of &amp;#35;12361&lt;/p&gt;</description><author>cpoole</author><pubDate>Fri, 24 Aug 2007 05:39:11 GMT</pubDate><guid isPermaLink="false">COMMENTED ISSUE: typo in src\NUnitLite\Runner\CommandLineOptions.cs, line 132 20070824053911A</guid></item><item><title>CREATED ISSUE: update copyright info in copyright information in NUnitLiteTests\Properties\AssemblyInfo.cs</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12412</link><description>is 2006, should be 2007&lt;br/&gt;</description><author>z00m1n</author><pubDate>Fri, 24 Aug 2007 03:47:43 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: update copyright info in copyright information in NUnitLiteTests\Properties\AssemblyInfo.cs 20070824034743A</guid></item><item><title>CREATED ISSUE: typo in src\NUnitLite\Runner\CommandLineOptions.cs, line 132</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12411</link><description>src&amp;#92;NUnitLite&amp;#92;Runner&amp;#92;CommandLineOptions.cs, line 132 reads&lt;br /&gt;    &amp;#35;if PocketPC &amp;#124;&amp;#124; WindowsCD &amp;#124;&amp;#124; NETCF&lt;br /&gt;but should probably be&lt;br /&gt;    &amp;#35;if PocketPC &amp;#124;&amp;#124; WindowsCE &amp;#124;&amp;#124; NETCF&lt;br/&gt;</description><author>z00m1n</author><pubDate>Fri, 24 Aug 2007 03:46:53 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: typo in src\NUnitLite\Runner\CommandLineOptions.cs, line 132 20070824034653A</guid></item><item><title>CREATED ISSUE: NUnitLite.sln still contains a reference to CppTests\CppTests.vcproj</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12410</link><description>see corresponding email&lt;br/&gt;</description><author>z00m1n</author><pubDate>Fri, 24 Aug 2007 03:45:33 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: NUnitLite.sln still contains a reference to CppTests\CppTests.vcproj 20070824034533A</guid></item><item><title>CREATED ISSUE: StackFilter still uses NUnitLite namespace</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12372</link><description>The StackFilter class looks for NUnitLite.Framework classes to eliminate from the stack even though we changed the namespace to be NUnit.Framework. The tests are also incorrect.&lt;br /&gt;&lt;br /&gt;In addition, the filter is currently removing classes in the middle of the call stack rather than just at the top as it should. We need more tests to confirm and fix this.&lt;br/&gt;</description><author>cpoole</author><pubDate>Tue, 21 Aug 2007 22:10:30 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: StackFilter still uses NUnitLite namespace 20070821101030P</guid></item><item><title>COMMENTED ISSUE: Incorrect preprocessor constant used in DisplayHelp()</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12361</link><description>At line 132 of CommandLineOptions.cs &amp;#40;the DisplayHelp&amp;#40;&amp;#41; method&amp;#41;, there is a preprocessor conditional block which uses the define WindowsCD. This should be WindowsCE.&lt;br/&gt;Comments: ** Comment from web user: cpoole ** &lt;p&gt;Fixed - that slipped in because my nant script uses NETCF&lt;/p&gt;</description><author>cpoole</author><pubDate>Tue, 21 Aug 2007 17:27:00 GMT</pubDate><guid isPermaLink="false">COMMENTED ISSUE: Incorrect preprocessor constant used in DisplayHelp() 20070821052700P</guid></item><item><title>CREATED ISSUE: Incorrect preprocessor constant used in DisplayHelp()</title><link>http://www.codeplex.com/NUnitLite/WorkItem/View.aspx?WorkItemId=12361</link><description>At line 132 of CommandLineOptions.cs &amp;#40;the DisplayHelp&amp;#40;&amp;#41; method&amp;#41;, there is a preprocessor conditional block which uses the define WindowsCD. This should be WindowsCE.&lt;br/&gt;</description><author>neilc</author><pubDate>Tue, 21 Aug 2007 16:33:23 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Incorrect preprocessor constant used in DisplayHelp() 20070821043323P</guid></item></channel></rss>