How can I overcome the buffer limitation using StreamReader.Re adTo

[=?Utf-8?B?UHVjY2E=?=]

Hi, I'm using VS 2005, ,.net 2 for C# windows application. I'm using Process
to run a C application and redirecting its standard output so I can read it
with StreamReader.Re adToEnd. It's only reading the 1st 5 lines or so when
there is about 30 lines of data.
I also tried using the Process.BeginOu tputReadlin and a
DataReceivedEvn tHandler to gather output but I also only get about 5 lines of
the data.
There seems to be a buffer size issue. Can someone tell me how can I
resolve this problem. Thank you.
--
Thanks.

[Jon Skeet [C# MVP]]

Pucca <Pu***@discussi ons.microsoft.c omwrote:

Hi, I'm using VS 2005, ,.net 2 for C# windows application. I'm using Process
to run a C application and redirecting its standard output so I can read it
with StreamReader.Re adToEnd. It's only reading the 1st 5 lines or so when
there is about 30 lines of data.
I also tried using the Process.BeginOu tputReadlin and a
DataReceivedEvn tHandler to gather output but I also only get about 5 lines of
the data.
There seems to be a buffer size issue. Can someone tell me how can I
resolve this problem. Thank you.

It should work fine. Do you know if your C application is actually
finishing? You should read from standard error as well as standard out
- otherwise if it's trying to write to standard error, it may be
blocking.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[=?Utf-8?B?UHVjY2E=?=]

Here is my code on first try to read the standard output. In the debug mode
I can see some lines of the data are read in but the process never has a
exited status. I even took away the time out value and it just hangs and
sits there and I can see the stream buffer hits a limit and hangs.
listFiles.WaitF orExit();
Is there a way to read all my data in without a buffer limitation? Thank you.

public static int GetNisFile(Syst em.Diagnostics. ProcessStartInf o psi,
ref DataTable dtAccounts,
ref ToolStripStatus Label slMain, ref StatusStrip ssMain, string
userOrGroup)
{

string accountFile="", output="";
int numOfAccounts = 0;
System.IO.Strea mReader fileOutput = null, myOutput = null;
System.Diagnost ics.Process listFiles;
try
{
listFiles = System.Diagnost ics.Process.Sta rt(psi);
if (listFiles != null)
{
myOutput = listFiles.Stand ardError;
fileOutput = listFiles.Stand ardOutput;
listFiles.WaitF orExit(30000);
if (listFiles.HasE xited)
{
// Read and display lines from the file until the end of
// the file is reached.
accountFile = fileOutput.Read ToEnd();
output = myOutput.ReadTo End();
if (accountFile != null && accountFile != "")
numOfAccounts =
CPAUnix.ParseAn dInsertAccounts (accountFile,
ref dtAccounts, ref slMain, ref ssMain, userOrGroup);
}
else
MessageBox.Show ("Time out retrieving NIS" + userOrGroup +
"accounts." ,
"PowerADvantage ");
}
else
MessageBox.Show ("Error starting process to read file.",
"PowerADvantage ");

return numOfAccounts;

}
catch (Win32Exception wex)
{
MessageBox.Show (wex.Message, "PowerADvantage ");
return numOfAccounts;
}
}
--
Thanks.
"Jon Skeet [C# MVP]" wrote:

Pucca <Pu***@discussi ons.microsoft.c omwrote:

Hi, I'm using VS 2005, ,.net 2 for C# windows application. I'm using Process
to run a C application and redirecting its standard output so I can read it
with StreamReader.Re adToEnd. It's only reading the 1st 5 lines or so when
there is about 30 lines of data.
I also tried using the Process.BeginOu tputReadlin and a
DataReceivedEvn tHandler to gather output but I also only get about 5 lines of
the data.
There seems to be a buffer size issue. Can someone tell me how can I
resolve this problem. Thank you.

It should work fine. Do you know if your C application is actually
finishing? You should read from standard error as well as standard out
- otherwise if it's trying to write to standard error, it may be
blocking.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[=?Utf-8?B?UHVjY2E=?=]

Here is my code using BeginOutputRead Line. This code doesn't have the time
out issue but it only returns 5 lines of data.

static System.Text.Str ingBuilder sb = new System.Text.Str ingBuilder();
static void proc_OutputData Received(object sender, DataReceivedEve ntArgs e)
{
sb.Append(e.Dat a);
}

public static int GetNisFile(Syst em.Diagnostics. ProcessStartInf o psi,
ref DataTable dtAccounts,
ref ToolStripStatus Label slMain, ref StatusStrip ssMain, string
userOrGroup)
{

string accountFile = "", output = "", line = "", theResult="";
int numOfAccounts = 0;
System.IO.Strea mReader fileOutput = null, myOutput = null;
System.Diagnost ics.Process listFiles = new Process();
listFiles.Start Info = psi;
try
{
String inputText;
int numInputLines = 0;
listFiles.Outpu tDataReceived += new
DataReceivedEve ntHandler(proc_ OutputDataRecei ved);
//listFiles = System.Diagnost ics.Process.Sta rt(psi);
// Use a stream writer to synchronously write the sort input.
listFiles.Start ();
//StreamReader nisReader = listFiles.Stand ardOutput;
listFiles.Begin OutputReadLine( );
listFiles.WaitF orExit();
theResult = sb.ToString();
listFiles.Cance lOutputRead();
listFiles.Kill( );
return numOfAccounts;

}
catch (Win32Exception wex)
{
MessageBox.Show (wex.Message, "PowerADvantage ");
return numOfAccounts;
}
}
--
Thanks.
"Jon Skeet [C# MVP]" wrote:

Pucca <Pu***@discussi ons.microsoft.c omwrote:

Hi, I'm using VS 2005, ,.net 2 for C# windows application. I'm using Process
to run a C application and redirecting its standard output so I can read it
with StreamReader.Re adToEnd. It's only reading the 1st 5 lines or so when
there is about 30 lines of data.
I also tried using the Process.BeginOu tputReadlin and a
DataReceivedEvn tHandler to gather output but I also only get about 5 lines of
the data.
There seems to be a buffer size issue. Can someone tell me how can I
resolve this problem. Thank you.

It should work fine. Do you know if your C application is actually
finishing? You should read from standard error as well as standard out
- otherwise if it's trying to write to standard error, it may be
blocking.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

Pucca <Pu***@discussi ons.microsoft.c omwrote:

Here is my code on first try to read the standard output. In the debug mode
I can see some lines of the data are read in but the process never has a
exited status. I even took away the time out value and it just hangs and
sits there and I can see the stream buffer hits a limit and hangs.
listFiles.WaitF orExit();
Is there a way to read all my data in without a buffer limitation? Thank you.

You need to read the data in a different thread, basically. I don't
have the time to write the code right now, but if you have one thread
reading the stdout and one reading stderr, you shouldn't see this
problem.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[=?Utf-8?B?UHVjY2E=?=]

Thanks Jon, I did read the article on the parent, child process deadlock
issue. I modified my code to use sync. read for the stderr and async. read
for the stadout. But, I'm still getting just a few lines of my stdout. I
ran the C application again and it gets over 100 lines of data. Thank you.
static System.Text.Str ingBuilder sb = new System.Text.Str ingBuilder();
static void proc_OutputData Received(object sender, DataReceivedEve ntArgs e)
{
sb.Append(e.Dat a);
}

public static int GetNisFile(Syst em.Diagnostics. ProcessStartInf o psi, string
parm,
ref DataTable dtAccounts,
ref ToolStripStatus Label slMain, ref StatusStrip ssMain, string
userOrGroup)
{

string accountFile = "", output = "", line = "", theResult="";
int numOfAccounts = 0;
String inputText;
int numInputLines = 0;
System.IO.Strea mReader fileOutput = null, myOutput = null;
System.Diagnost ics.Process listFiles = new Process();
//listFiles.Start Info = psi;
try
{
listFiles.Outpu tDataReceived += new
DataReceivedEve ntHandler(proc_ OutputDataRecei ved);
listFiles.Start Info = new ProcessStartInf o(Application.S tartupPath +
"\\ypcat.ex e", parm);
listFiles.Start Info.UseShellEx ecute = false;
listFiles.Start Info.RedirectSt andardOutput = true;
listFiles.Start Info.RedirectSt andardError = true;
//listFiles = System.Diagnost ics.Process.Sta rt(psi);
// Use a stream writer to synchronously write the sort input.
if (listFiles.Star t())
{
//StreamReader nisReader = listFiles.Stand ardOutput;
listFiles.Begin OutputReadLine( );
string error = listFiles.Stand ardError.ReadTo End();
listFiles.WaitF orExit();
if(listFiles.Ha sExited)
theResult = sb.ToString();
listFiles.Cance lOutputRead();
listFiles.Close ();
}
return numOfAccounts;

}
catch (Win32Exception wex)
{
MessageBox.Show (wex.Message, "PowerADvantage ");
return numOfAccounts;
}
}
--
Thanks.
"Jon Skeet [C# MVP]" wrote:

Pucca <Pu***@discussi ons.microsoft.c omwrote:

Here is my code on first try to read the standard output. In the debug mode
I can see some lines of the data are read in but the process never has a
exited status. I even took away the time out value and it just hangs and
sits there and I can see the stream buffer hits a limit and hangs.
listFiles.WaitF orExit();
Is there a way to read all my data in without a buffer limitation? Thank you.

You need to read the data in a different thread, basically. I don't
have the time to write the code right now, but if you have one thread
reading the stdout and one reading stderr, you shouldn't see this
problem.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

On Aug 6, 8:58 am, Pucca <Pu...@discussi ons.microsoft.c omwrote:

Thanks Jon, I did read the article on the parent, child process deadlock
issue. I modified my code to use sync. read for the stderr and async. read
for the stadout. But, I'm still getting just a few lines of my stdout.

Without full code to run ourselves, it's pretty tricky to diagnose
this.

I suggest you first swap out the original process for a "dummy"
process written in C# which just writes 100 lines of output to both
stdout and stderror - then come up with a short but complete program
in C# which shows the problem occurring. That way we can all look at
the same issue.

Jon

[=?Utf-8?B?UHVjY2E=?=]

Ok, I will do that. Sounds like a good test. Also, I forgot to mention that
I'm running on Windows 2000 server. Would this be the problem?
--
Thanks.
"Jon Skeet [C# MVP]" wrote:

On Aug 6, 8:58 am, Pucca <Pu...@discussi ons.microsoft.c omwrote:

Thanks Jon, I did read the article on the parent, child process deadlock
issue. I modified my code to use sync. read for the stderr and async. read
for the stadout. But, I'm still getting just a few lines of my stdout.

Without full code to run ourselves, it's pretty tricky to diagnose
this.

I suggest you first swap out the original process for a "dummy"
process written in C# which just writes 100 lines of output to both
stdout and stderror - then come up with a short but complete program
in C# which shows the problem occurring. That way we can all look at
the same issue.

Jon

[Jon Skeet [C# MVP]]

Pucca <Pu***@discussi ons.microsoft.c omwrote:

Ok, I will do that. Sounds like a good test. Also, I forgot to mention that
I'm running on Windows 2000 server. Would this be the problem?

Shouldn't be, no.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[=?Utf-8?B?UHVjY2E=?=]

I created 2 applications as you said and it works! So, I use the new C#
application and instead of calling the dummy program I called my C
application and display the output to a textbox and that works too! Now, I'm
really confused about why it doesn't work in my program.
--
Thanks.
"Jon Skeet [C# MVP]" wrote:

On Aug 6, 8:58 am, Pucca <Pu...@discussi ons.microsoft.c omwrote:

Thanks Jon, I did read the article on the parent, child process deadlock
issue. I modified my code to use sync. read for the stderr and async. read
for the stadout. But, I'm still getting just a few lines of my stdout.

Without full code to run ourselves, it's pretty tricky to diagnose
this.

I suggest you first swap out the original process for a "dummy"
process written in C# which just writes 100 lines of output to both
stdout and stderror - then come up with a short but complete program
in C# which shows the problem occurring. That way we can all look at
the same issue.

Jon