Tuesday, March 9, 2010

Test-Driven Development Links

Test-driven development (TDD) is an advanced technique of using automated unit tests to drive the design of software and force decoupling of dependencies. The result of using this practice is a comprehensive suite of unit tests that can be run at any time to provide feedback that the software is still working.

Methodology / Approach

TDD Blog Roll

Software – Commercial Test Runners

Software – Open-Source Test Runners

Software – Open-Source Test Runner Complements

Software – Open-Source Mock Objects

Software - Unit Testing & Tools for Xml Web Services

Books (Linked to the greatness that is www.bookpool.com )

Articles

Software - Code Coverage (How much code actually executed?)

Refactoring:

Sites:

Software:

Books:

Development Methodologies Links

MSF - http://msdn.microsoft.com/vstudio/enterprise/msf/

FDD

Agile - http://www.agilemanifesto.org/

xP –

SCRUM

Visual Studio 2005 Team System Links


Posted by at No comments:
Labels: ,

Monday, March 8, 2010

ASP.NET Starter Kits and Community Projects

The ASP.NET 2.0 Starter Kits for Visual Web Developer are fully functional sample applications to help you learn ASP.NET 2.0 and accomplish common Web development scenarios. Each sample is complete and well-documented so that you can use the code to kick start your Web projects today! These kits, once downloaded are integrated directly into the Visual Web Developer 2005 Express Edition or Visual Studio 2005 experience.



Posted by at No comments:
Labels:

IIS Issue: Unexpected Error 0x8ffe2740 Occurred

If you are using IIS 5.1 on XP and are being presented with an "Unexpected Error 0x8ffe2740 Occurred" error message when trying to start your website from the IIS Admin panel, then it is likely that you have a port conflict on your system. That's the easy part, now what do you do to track this conflict down and fix it?

Well, that actually isn't that hard either. By default IIS will try and bind itself to TCP port 80, so the first thing to do is track down which process is binding itself to this port. This could be anything from another webserver (such as Skype), or in my case Apache. To do this, open a command prompt window and type in the following;

netstat -anop TCP|find ":80 "

This will give you some details of what process is using TCP port 80, and unless you have a multihomed system you should only get one result here. The only information that you really need to be concerned about is the number that is display on the far right hand side. This is the PID (Process Identifier) which is a unique number given to a process by the system when it is initiated.

The next step is to match this PID with an actual process that you can identify. There are several ways you can do this, but probably the easiest way is to go back to your command prompt window and type this in (where the number 1234 is the PID number from the previous step);

tasklist /SVC /FI "PID eq 1234"

What this will do is associate the PID number you enter with a process name which will be displayed on the far left, and on the far right will be the name(s) of any related services.This should give you a pretty clear picture of what software is binding itself to TCP port 80, and from there it is a matter of either reconfiguring that software to use a different port number or disabling it while IIS is in use. Of course on the flip side you could always reconfigure IIS to use a different port number as well. Either way, you should now be able to take action so you can start your website from the IIS Admin panel.
Posted by at No comments:
Labels: ,
Subscribe to: Posts (Atom)