Thanks for the response. What was actually happening though, is that there
was an environment variable ERRORLEVEL set, which was masking the Command
Window's ERRORLEVEL facility. So, before doing anything significant, I did
SET ERRORLEVEL=
to clear the variable. And all is well now.
Gem
"Morten Wennevik" <Mo************@hotmail.com> wrote in message
news:opsiopmgl8klbvpo@pbn_computer...
Hi Gemma,
If you launch csc.exe as a process while also setting output to your own
stream anything output from 'csc.exe /nologo' will either be an error or a
warning. You will have to read each line to see which.
--
Happy Coding!
Morten Wennevik [C# MVP]