Daniel Cazzulino's Blog

By default, when you implement an interface in a class, you get the following for properties:

Every now and then, when trying to do something in MSBuild, I hit a roadblock (or maybe just some unintuitive “feature”) and I’m left thinking “gosh, now I have to create a custom MSBuild task for this one-liner that is SO trivial in plain C#!”.

It’s quite common to refer to $(DevEnvDir) in a project, such as to specify the path to a referenced assembly, or to execute a tool on a build event or a target. It’s right there in the UI after all, why not use it?

You probably know I’m an advocate of a particular way of doing extension methods that I call the “Extension Method Entry Point Pattern”, which makes it easier to mock them.

I got this question a couple times already so I’ll save keystrokes and post here.

This functionality has been discussed and requested as a feature for a future version of NuGet.

IE is not my default browser. But still some links have to be sent to it in order for the right thing to happen (i.e. Microsoft Lync invitations, Live Meeting, InfoPath forms, etc.). So far I had the multi-click solution of opening IE, then clicking on a toolbar bookmark.

In case you didn’t notice, VS2010 adds a new property to assembly references in the properties window: Embed Interop Types: