<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="0.92" xml:base="http://www.testingreflections.com">
<channel>
 <title>testingReflections.com - .NET</title>
 <link>http://www.testingreflections.com/taxonomy/view/or/92</link>
 <description></description>
 <language>en</language>
<item>
 <title>Essential Visual Studio Plugins... Ghost Doc, TestDriven.NET, Smart Paster and more...</title>
 <link>http://www.testingreflections.com/node/view/3231</link>
 <description>[textile].NET Developer (and friend) "Joe Field":http://joefield.mysite4now.com/blogs/blog/ sent me this link...

"Visual Studio Add-Ins Every Developer Should Download Now":http://msdn.microsoft.com/msdnmag/issues/05/12/VisualStudioAddins/default.aspx

I already knew about "Test Driven .NET":http://www.testdriven.net/ but what is going to come in handy for me right now is "GhostDoc":http://www.roland-weigelt.de/ghostdoc since I am documenting an API (that Joe and I developed) for a client before I move focus onto another project with a new client.

&lt;blockquote&gt;
The goal of GhostDoc is to automate the tedious parts of writing XML comments by looking at the name of your class or method, as well as any parameters, and making an educated guess as to how the documentation should appear based on recommended naming conventions. This is not a replacement for writing thorough documentation of your business rules and providing examples, but it will automate the mindless part of your documentation generation.
&lt;/blockquote&gt;</description>
<pubDate>Fri, 10 Feb 2006 06:58:26 -0600</pubDate></item>
<item>
 <title>NUnit Test Runner and Profiler for Visual Studio</title>
 <link>http://www.testingreflections.com/node/view/3115</link>
 <description>[textile]Looks interesting... Will have to investigate this tool...&lt;br /&gt;
&lt;br /&gt;
"MailFrame NUnit TestRunner":http://www.mailframe.net/Products/TestRunner/2005/&lt;br /&gt;
&lt;br /&gt;
I like the look of the visual integration with the Visual Studio editor...</description>
<pubDate>Thu, 05 Jan 2006 08:35:11 -0600</pubDate></item>
<item>
 <title>"Unable to generate a temporary class" with SWExplorerAutomation...</title>
 <link>http://www.testingreflections.com/node/view/2592</link>
 <description>[textile]While helping someone get started with evaluating "SWExplorerAutomation":http://home.comcast.net/~furmana/SWIEAutomation.htm (I'll call it SEA if you don't mind) on a client's site, we encountered an error almost as soon as we tried to use it... but it turned out that it had nothing to do with the tool and everything to do with a bug in an MS Security Patch... "read on to find out more":http://www.testingreflections.com/node/view/2592</description>
<pubDate>Mon, 22 Aug 2005 04:56:08 -0500</pubDate></item>
<item>
 <title>Expert .NET Delivery Using NAnt and CruiseControl.NET</title>
 <link>http://www.testingreflections.com/node/view/2455</link>
 <description>At first glance, building and deploying applications seem simple enough. But in fact, difficult releases without any confidence or processes backing them are very common. Integration and management of a new deployment can be laborious and fraught with risk. So as team size and volume of projects grow, management becomes more difficult and risk more pronounced. This book is a guide to the implementation of good processes in a .NET environment. Author Marc Holmes focuses on actual implementation, and details patterns and anti-patterns to watch out for. He also provides a practical and in-depth look at NAnt and CruiseControl.NET, and solutions to common problem scenarios.</description>
<pubDate>Mon, 04 Jul 2005 01:02:36 -0500</pubDate></item>
<item>
 <title>Rhino.Mocks v. 2.0 Announced. Yes, it's a Mock Object Framework.</title>
 <link>http://www.testingreflections.com/node/view/2450</link>
 <description>&lt;p&gt;&lt;a href="http://www.ayende.com/Blog/"&gt;Ayende &lt;/a&gt;has &lt;a href="http://www.ayende.com/Blog/RhinoMocks20Released.aspx"&gt;announced&lt;/a&gt; that he's released &lt;a href="http://www.codeproject.com/useritems/Rhino_Mocks_Version_20.asp"&gt;Rhino.Mocks v. 2.0&lt;/a&gt;: his own version of what he'd like in a Mock Object framework. I haven't yet got a chance to try it out, but it certainly sounds interesting!&lt;/p&gt; &lt;p&gt;"Rhino.Mocks is an attempt to create easier way to build and use mock objects and allow better refactoring support from the current tools. It's a hybrid approach between the pure Record/Replay of &lt;a href="http://sourceforge.net/projects/easymocknet/"&gt;EasyMock.Net&lt;/a&gt;'s model and &lt;a href="http://www.nmock.org/"&gt;NMock&lt;/a&gt;'s expectation based model. Rhino.Mocks originated from &lt;a href="http://sourceforge.net/projects/easymocknet/"&gt;EasyMock.Net&lt;/a&gt; and attempt to improve on their model to create easy to use and power mocking framework. It's free for use and modification for free and commercial software.&lt;/p&gt;</description>
<pubDate>Mon, 04 Jul 2005 00:56:34 -0500</pubDate></item>
<item>
 <title>Technique for Manipulating the HttpContext within NUnitAsp tests</title>
 <link>http://www.testingreflections.com/node/view/2438</link>
 <description>I created a Setup.aspx file that would allow me to make requests to it and pass in a static method that I wanted to call, and as a result, any code that ran inside of it would run inside the webs application domain and have access to the Session and HttpContext. Author: Robin Curry Published: June 27, 2005</description>
<pubDate>Mon, 04 Jul 2005 00:58:55 -0500</pubDate></item>
<item>
 <title>Rhino Mocks: .NET mocking framework</title>
 <link>http://www.testingreflections.com/node/view/2398</link>
 <description>A dynamic mock object framework for the .Net platform. Its purpose is to ease testing by allowing the developer to create mock implementations of custom objects and verify the interactions using unit testing. Rhino.Mocks is an attempt to create easier way to build and use mock objects and allow better refactoring support from the current tools. It's a hybrid approach between the pure R</description>
<pubDate>Sun, 26 Jun 2005 13:22:27 -0500</pubDate></item>
<item>
 <title>Continuous Integration &amp; .NET (2): Continuous Integration and beyond...</title>
 <link>http://www.testingreflections.com/node/view/2169</link>
 <description>While unfamiliar to many developers, Continuous Integration is not a new concept at Microsoft, as is evident by Steve McConnell's observation. Consequently, in this second installment of a two-part article, I examine the setup of a version-control system and configuration of a Continuous Integration tool that runs off of the version-control system in the .NET environment. I then integrate these tools into the build process to test for conformance with the Microsoft .NET Framework Design Guidelines, and finally address the issue of code-coverage testing.</description>
<pubDate>Thu, 19 May 2005 00:37:55 -0500</pubDate></item>
<item>
 <title>Continuous Integration &amp; .NET (1): Weaving together an open-source solution</title>
 <link>http://www.testingreflections.com/node/view/2166</link>
 <description>Several basic tools used to support Continuous Integration were ported to the .NET environment during the 1.0 release of the Framework. Other tools, such as CruiseControl and Clover, have been ported more recently. Furthermore, certain other tools such as NDoc are indigenous to .NET and only conceptually related to their Java counterparts (Java Doc, in this case). For the most part, articles written to date about these tools have addressed only a subset of the tools (usually NAnt and NUnit), thus failing to weave together a holistic Continuous Integration solution. Moreover, the unit-testing examples are function based and fail to address the database-driven reality of today's enterprise applications.</description>
<pubDate>Thu, 19 May 2005 00:38:53 -0500</pubDate></item>
<item>
 <title>Nullable type performance</title>
 <link>http://www.testingreflections.com/node/view/2063</link>
 <description>Warning! &lt;A href="http://davidkean.net/archive/2005/04/25/393.aspx"&gt;Nullable types considered hazardous to your performance&lt;/A&gt;.&lt;img src="http://codebetter.com/aggbug.aspx?PostID=62426" width="1" height="1"&gt;</description>
<pubDate>Tue, 26 Apr 2005 01:16:38 -0500</pubDate></item>
<item>
 <title>Open Source .NET Development: ASpell.NET Case Study</title>
 <link>http://www.testingreflections.com/node/view/1526</link>
 <description>This chapter is a simple but realistic case study of using Open Source tools in everyday development. In particular, this chapter uses ASpell, a commercial-caliber spell checking component that supports twenty-some different language dictionaries, as an example.Author: Brian NantzPublished: Jan 7, 2005(Sample chapter extracted from Open Source .NET Development: Programming</description>
<pubDate>Sat, 29 Jan 2005 03:48:02 -0600</pubDate></item>
<item>
 <title>Advanced Techniques with NUnitAsp</title>
 <link>http://www.testingreflections.com/node/view/1525</link>
 <description>Keeping bugs out of existing code during new development has always been a huge problem. However a new methodology, Test Driven Development (TDD), is helping to change that. The two main principles of this methodology are: 1) Never write a single line of code unless you have a failing automated test, and 2) Eliminate duplication.In principle this makes sense - we'd all love to have a thousand automated tests, running at the click of a button or command line, which guarantees that our application works. There's even a popular open source tool, NUnit, which provides a framework for running automated unit tests. While this is very popular with class libraries that just manipulate data structures, it is much more difficult with GUIs.</description>
<pubDate>Sat, 29 Jan 2005 03:45:19 -0600</pubDate></item>
<item>
 <title>Test Driven Development Using NUnit in C#</title>
 <link>http://www.testingreflections.com/node/view/1524</link>
 <description>When sitting down to create an application, many developers start by writing the code. Test Driven Development emphasizes the opposite, stressing the need to prepare test scenarios or test cases before writing the code itself. This seemingly backwards approach has some benefits. First of all, it requires that the programmer be very clear about what tests the program should pass and what test it should fail, bringing such concerns to the forefront of the software design process. Furthermore, by meticulously detailing what tests a system should pass and fail we can use tools to automate most of our tests. An automated job is one that's always very, very easy to do. These automated tests are meant to be run every time there's a code change and are referred to as unit tests.</description>
<pubDate>Sat, 29 Jan 2005 03:44:37 -0600</pubDate></item>
<item>
 <title>Data Input Validation Using ASP.NET Forms</title>
 <link>http://www.testingreflections.com/node/view/1523</link>
 <description>&lt;p&gt;&lt;a href="http://www.consultantsguild.com/KirkMiller.html"&gt;Kirk Miller&lt;/a&gt; (another &lt;a href="http://www.consultantsguild.com/index.html"&gt;Consultants Guild&lt;/a&gt; member) has a great introductory&amp;nbsp;&lt;a href="http://blogs.consultantsguild.com/index.php/kmiller/2005/01/25/data_input_validation_using_asp_net_form"&gt;post&lt;/a&gt; on data input validation for ASP.NET forms.&lt;/p&gt;</description>
<pubDate>Sat, 29 Jan 2005 04:08:42 -0600</pubDate></item>
<item>
 <title>SharpDevelop develops NUnit integration</title>
 <link>http://www.testingreflections.com/node/view/1520</link>
 <description>&lt;a href="http://www.icsharpcode.net/OpenSource/SD/WhatsNew.aspx"&gt;Oh this is cool.&lt;/a&gt;  &lt;a href="http://www.icsharpcode.net/OpenSource/SD/default.aspx"&gt;SharpDevelop&lt;/a&gt;, the open source .NET editor, has built in NUnit integration. I'm still not sure what that really means, but I intend to find out. Hopefully it will be just like the JUnit integration found in similar Java projects.</description>
<pubDate>Sat, 29 Jan 2005 03:57:23 -0600</pubDate></item>
</channel>
</rss>
