SnowFrog - 2012-06-13

Hi there;

I have been working on improvements to SQL2Doxygen so it can parse our 5000+ SQL procedures. After frustrating hours of trials I contacted Chris Oldwood the creator of SQL2Doxygen and he says the following variations work for him.

INPUT_FILTER = "Powershell.exe ..\sql2doxygen.ps1"
This does not work for me. It must be
INPUT_FILTER= Powershell.exe -File "..\sql2doxygen.ps1"
If the -File is not there it does not work. But with the INPUT_FILTER set that way all is right.

My issue is that the project contains both C# and SQL and I would like to document both together (I'll get back to TAGFILES further down".
So I tried to use the
FILTER_PATTERNS = *.SQL=Powershell.exe ..\sql2doxygen.ps1
Now it does not seem to matter if I use double quote, single quote, both it does does not seems to work. In this case if I use the "-File" as I did in the INPUT_FILTER then I get an outright error.

Since Chris tells me that this works for him I would have a tendency to believe that it is a platform issue. I am running on Windows 7 64 bits. I also upgraded today to Doxygen 1.8.1.1 to make sure I got the very latest.

Are there any known issues with this? or does anyone know why the calls are actually behaving differently  from INPUT_FILTER to FILTER_PATTERNS.

Please help

NOTE: I have tried to solve part of this issue in splitting the parsing with TAG files but this did not seem to work either, but I will investigate further before complaining.

Note that I can run the new sql parser through my 5000+ SPs from within powershell with no problems, just time ;-)