C# ala ASP .Net - Web App needs to run external appliation

[Xataraxx]

I'm a little new to this environment, so if this is a silly question I
apologize ahead of time. :-)

I have a web application written in ASP .Net / C#. This web app needs
to run an external Windows cmd line application. No problem so far.
I've tested it and it seems to work fine.

Now here's my question:

When multiple users are hitting the web app and attempting to run the
external application simultaneously, what will happen? Do I need to
make sure that only one user will hit that section of code at a time
time, or will each request to run the external application result in a
new process/thread?

[Nicholas Paldino [.NET/C# MVP]]

Xataraxx,

Every call to the external app is going to cause another process to be
spawned.

The only concurrency issues you have to worry about is other resources
the process might be accessing.

Also, if you are doing this in a web app, you might want to consider
writing the code into a library (at which point, your concurrency issues are
valid, as well as any resource sharing issues), as spawning a large number
of processes at the same time is not going to be good for throughput.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Xataraxx" <Xa******@gmail .comwrote in message
news:11******** **************@ q75g2000hsh.goo glegroups.com.. .

>
I'm a little new to this environment, so if this is a silly question I
apologize ahead of time. :-)

I have a web application written in ASP .Net / C#. This web app needs
to run an external Windows cmd line application. No problem so far.
I've tested it and it seems to work fine.

Now here's my question:

When multiple users are hitting the web app and attempting to run the
external application simultaneously, what will happen? Do I need to
make sure that only one user will hit that section of code at a time
time, or will each request to run the external application result in a
new process/thread?

[Xataraxx]

On Apr 4, 12:43 pm, "Nicholas Paldino [.NET/C# MVP]"
<[e-mail] d.caspershouse. comwrote:

Every call to the external app is going to cause another process to be
spawned.

Ok, cool. that's what I thought would be happening, but I wasn't
sure.

Also, if you are doing this in a web app, you might want to consider
writing the code into a library (at which point, your concurrency issues are
valid, as well as any resource sharing issues), as spawning a large number
of processes at the same time is not going to be good for throughput.

That external app will become a DLL at some point. Unfortunately I'm
really pressed for time @ the moment. It was written by somebody else
in C and it's been such a long time since I've used C, that it's
nearly unrecognizable to me now. Unfortunately, it's just going to
have to wait until after the initial product release.

Fortunately, we're only releasing a Beta. So we can let some of the
niceties slide for now. :-)

Anyway,

thanks for the help!