ScottGu's Blog : Tip/Trick: Patterns and Practices Guidance Explorer for .NET and ASP.NET

 

.NET and ASP.NET Guidance Explorer

Source: ScottGu's Blog : Tip/Trick: Patterns and Practices Guidance Explorer for .NET and ASP.NET

Scripting with Windows PowerShell

How lame. Just about all links to PowerShell's new version RC2 are dead links. When will MS fix them!?!?! 

Link to Scripting with Windows PowerShell

LearnSqlServer.com - SQL Server Training and Tutorials ON VIDEO, SQL Server 2005 Video Training, Free SQL Server 2005 Videos

 

Link to LearnSqlServer.com - SQL Server Training and Tutorials ON VIDEO, SQL Server 2005 Video Training, Free SQL Server 2005 Videos

InfoQ: Book Excerpt: Implementing Lean Software Development: From Concept to Cash

 

The 7 Principles of Lean Software Development:

1. Eliminate Waste
   The three biggest wastes in software development are: Extra Features, Churn, Crossing Organizational Boundaries.
2. Build Quality In
   If you routinely find defects in your verification process, your process is defective.
3. Create Knowledge
   Planning is useful. Learning is essential. Predictable performance is driven by feedback.
4. Defer Commitment
   Abolish the idea that it is a good idea to start development with a complete specification.
5. Deliver Fast
   Lists and queues are buffers between organizations that simply slow things down.
6. Respect People
   Engaged, thinking people provide the most sustainable competitive advantage.
7. Optimize the Whole
   Brilliant products emerge from a unique combination of opportunity and technology.

Source: InfoQ: Book Excerpt: Implementing Lean Software Development: From Concept to Cash

InfoQ: Testing Ajax Applications with Selenium

 

Testing Ajax Applications with Selenium

Source: InfoQ: Testing Ajax Applications with Selenium

InfoQ: Why Would a .NET Programmer Learn Ruby on Rails?

Good article, worth reading! 

Link to InfoQ: Why Would a .NET Programmer Learn Ruby on Rails?

The Pope's Monopoly on Reason

The Pope's Monopoly on Reason

Good article!

Remote Debugging with WinDbg

Taken From:

Application debugging in a production environment
Author : Hans De Smaele
Published : September 12, 2004

 
Personally, I like WinDbg the most to do remote debugging. Not only is this the most
powerful debugger, but it has also the most possibilities to connect computers with each
other. In some scenarios, you can connect up to 5 computers to debug a station !
Note: Check the WinDbg documentation for more information about how to setup
remote debugging.
Application debugging in a production environment
Version 1.1

100
An easy way to debug user applications (not kernel problems) with WinDbg is by
installing WinDbg on the debugging station and "DbgSvr" (process server) on the remote
computer.
Give the command below on the remote computer :
DbgSvr –t tcp:port=9999
And on the debugging computer, where WinDbg is located, run :
WinDbg –premote tcp:server=<remote station name>, port=9999 –p <PID>
And there you go !