Posted on August 20th, 2008%
I needed to download Lutz Roeder’s .Net Reflector on a new machine, so I did a Google search, and saw this as the first item listed:
.NET Reflector
A CLR class browser with XML documentation viewer, type search, disassembler and C#/VB view.
Clicking on the link, I was taken to http://www.red-gate.com/products/reflector/ and read this:
Red Gate has recently acquired .NET Reflector. We will continue to maintain a free version for the benefit of the community. For more information on the deal, please see the interview on Simple-Talk.
Well how about that.
. . .
→ Read More: Lutz Roeder’s .Net Reflector is now Red Gate’s .Net Reflector
Posted on August 18th, 2008%
A while back, I wrote a blog post, A quick introduction to Nant, which gave, well, a quick introduction to building C# libraries using NAnt.
Since then, I’ve been using NAnt to do a lot more — notably, to run unit tests and to report on test coverage (using NCover and NCoverExplorer). The usage is pretty straightforward, and I think you’ll see how each step builds on the previous step.
- To run a default build (excluding unit tests):
nant
- To build all projects and unit tests (but don’t run :
nant build-tests
- To build all projects and unit tests, and run tests using NUnit:
nant test
- To build all projects and unit tests, and run tests using NCover to generate coverage reports:
nant cover
- To build all projects and unit tests, run tests using NCover to generate coverage reports, and open those reports in NCoverExplorer:
nant coverex
The sample below is my NAnt build file. A few notes first.
- There are only two projects referenced: Project1 and Project1.Tests. Repeat the appropriate sections to build against additional projects.
- nunit-console.exe is expected to be in the system path.
- nunit-console.exe, ncover.console.exe, and ncoverexplorer.exe are expected to be in the system path. I recommend you download and install TestDriven.Net to have all of these in a convenient place.
Now, on to the build file. It should be self-explanatory, but I added some XML comments for your convenience.
. . . → Read More: Building with NAnt (and NUnit, and NCover, and NCoverExplorer)
Posted on August 15th, 2008%
I recently ordered Verizion FIOS TV. Since I already have home phone and Internet service from Verizon, and wireless service from Verzion, I wanted to make sure I am getting a bundled rate. (They offer a bunch of “bundle prices”.) I went into an online chat with a Verizon customer representative. Here’s what happened.
. . . → Read More: Verizon: Pricing based on who you talk to
Posted on August 8th, 2008%
Back in July 2008, Microsoft released the Source Code Analyzer for SQL Injection, a “static code analysis tool for finding SQL Injection vulnerabilities in ASP code.” With the large number of SQL injection attacks occurring recently, running this tool against your ASP-based web sites is important. (It’s not the only thing you should do, but it’s at least one thing you should do!)
The tool itself is composed of two command-line tools:
msscasi_asp.exe, which reviews an ASP file and outputs an XML file with vulnerability warnings.msscasi_view.cmd, a script which opens the generated XML file for viewing in a web application window.
One limitation is that you can’t run these utilities on more than one file — but you can run each of the utilities on every ASP file on your computer by running a batch file.
. . . → Read More: Identifying ASP pages vulnerable to SQL injection attacks using Microsoft’s Source Code Analyzer
