I've set up a bunch of schema install and upgrade scripts with names like 0.0.0.1.config. I would like to add these to my Visual Studio projects, so that I can see them along with all the other artefacts. But Visual Studio expects a .config file to contain XML, not SQL, so it reports parse errors on them at compile time. Obviously they go away if I exclude the files from the project but then I have to go to another application to see and manage them. I couldn't tell Visual Studio that .config means SQL because in most cases, of course, it *does* mean XML content. I can't find a way of instructing Visual Studio that a particular file should be treated in a particular way, but is there a way of including these files in projects without getting parse errors? Or is it acutally essential to give them a .config extension (I guess mojoPortal won't process them if they aren't so named)?