LINQ (language integrated query) is one of the new features provided with VS 2008 and .NET 3.5. LINQ makes the concept of querying data a first class programming concept in .NET, and enables you to efficiently express queries in your programming language of choice. One of the benefits of LINQ is that it enables you to write type-safe queries in VB and C#. This means you get compile-time checking of your LINQ queries, and full intellisense and refactoring support over your code: While writing type-safe queries is great for most scenarios, there are cases where you want the flexibility to dynamically construct queries on the fly.
Jim Newkirk is blogging about the down side of setup and teardown methods in test classes, and why you shouldn’t use them. Setup and teardown methods attract entropy faster than an outsource programmer with his first patterns book. Jim’s new framework, xUnit.NET doesn’t have primitives for setup and teardown, although it sounds like there are mechanisms that could be used to accomplish the same kind of thing. Roy feels that xUnit.NET isn’t quite there yet. I think that Roy’s perspective will be reflected by lots of folks who have become used to NUnit (et al) over the past six years. I think that Jim is on the right track, but I’m the kind of guy that feels that a test class’s greatest responsibility is to document behavior in the clearest possible way, even if that means sacrificing design qualities best reserved for functional code – like reuse. Dependency Patterns: Optional Dependencies and Primal Dependenci
Cutting Edge: Canceling Server Tasks with ASP.NET AJAX -- MSDN M Cutting Edge Canceling Server Tasks with ASP.NET AJAX Dino Esposito Code download available at:CuttingEdge2007_08.exe(167 KB) Last month I built a framework to monitor ongoing server-side tasks from the client.