Daniel Cazzulino's Blog

Someone asked me how to mock a dynamic object with Moq, which might be non-obvious.

I’m spiking ideas on how to make my regular expressions easier to read and maintain for the dev who comes after me (that could be myself in 3 months, meaning I will surely have forgotten everything about how that crazy regex worked).

Is it just me or the X220 is just plain better in almost all relevant fronts?

I’m not advocating *private* reflection (invoking private/internal fields, properties and methods), but we all know that there are those corner cases where you just can’t avoid it. And there’s a whole lot of scenarios when there are legitimate uses of reflection itself that can also leverage this very cool dynamic syntax (i.e. invoking generic methods where you don’t know the type at compile-time, etc.). In these cases, your code goes from pristine-looking C# to crappy unreadable reflection code.

From the documentation:

From the project home page:

In previous versions of the Web API, you could query your REST endpoints that exposed an IQueryable<T> server-side, kinda “Linq to WCF” as @gblock said. This was immensely useful and an important driver (among others) for me to move away from Astoria ADO.NET Data Services. That functionality is gone now (vote to get it back!).

Given the many cross-cutting concerns you can cover using the new Web API pipeline,  it’s not a bad idea to have a bunch of integration-style tests that cover the actual running service end to end.