I have some MSBuild files in my VS 2008 solution whose default “open with” editor is a custom batch job that runs the file against MSBuild.

When searching this morning in my database project, my batch jobs all started running!  Ack.  What’s going on is that VS is using the default “open with” editor to open the file for searching.

I need to submit a bug to the VS 2008 list.  This behavior is, um, sub-optimal.