Daniel Cazzulino's Blog
-
Locating the active item in the solution explorer
Say you are working with a code file. At some point, you "Go To Definition" of another type, and now you have its code file opened. Or maybe you just run the solution to debug a weird issue that's happening, turn on "break when exception is thrown" option, and just when the exception is thrown, Visual Studio gets activated, and you get the relevant code file opened at the appropriate location.
-
For those that think Microsoft Connect is useless
A while back I reported both through my weblog and Microsoft Connect what I thought was a serious flaw in the WPF validation infrastructure for ValidationRule and Binding. The issue, in short was:
-
Is Adobe AIR really a v1 product?
-
Expression tree usage in ASP.NET MVC Preview 2 rocks!
The latest MVC release adds some pretty cool usage of LINQ expression trees. It's another example of how cool (and WAY beyond querying) LINQ is.
-
Installing Windows Live Writer on Windows 2008
How long can it take to update a crappy installer and remove a hard-coded platform check?? Whatever...
-
How to install MySQL on Windows 2008
When you finish the setup, the configuration wizard may not start, and upon starting it manually, you might get:
-
Why do we need yet another .NET mocking framework?
I got this question a couple times in the past MIX08 at Las Vegas. And this is a very valid question indeed, given that there's already Rhino, EasyMock, TypeMock and NMock (to name a few). So why did we give you Moq?
-
HP MediaSmart Server does NOT support 64-bit clients???
-
How to get rid of the auto-generated #region for implemented interfaces
I HATE this default so much. Every stupid interface gets its own #region in my code file. I wonder who thought regions were so cool...
-
How to hide System.Object members from your interfaces
Sometimes, System.Object methods (Equals, GetHashCode, GetType and ToString) only contribute clutter to VS intellisense. Everyone knows those members are always there, yet they are seldom used explicitly. This is especially important (and annoying) for fluent APIs that define the flow of invocations in terms of interfaces and usually have few members at each "step" of the statement.