C# Calling Executable or DLL

[guxu@hotmail.com]

Can anyone tell me the prons and cons having C# program calling an
executable or DLL?
I always do not like the idea of having one executable calling another
executable since I can have more control by calling interfaces exposed
from a DLL. In my situation, I need to watch for a certain event and
exe can only give me a return code. Any pros using an exe?

[Stoitcho Goutsev \(100\)]

Re: C# Calling Executable or DLL

DLL is contains code tha can be shared between applications where on the
other hand the exe (application) uses dlls and don't expose any
functionaluty for the others to reuse. I say usually because it doesn't have
to be like this. There are several different ways for an exe to expose
functionality for reuse, but they come with a cost.

My advice is to use DLLs that what they are for.


--
HTH
Stoitcho Goutsev (100)

<guxu@hotmail.c omwrote in message
news:1161095899 .076374.104290@ m73g2000cwd.goo glegroups.com.. .

Can anyone tell me the prons and cons having C# program calling an
executable or DLL?
I always do not like the idea of having one executable calling another
executable since I can have more control by calling interfaces exposed
from a DLL. In my situation, I need to watch for a certain event and
exe can only give me a return code. Any pros using an exe?
>

[guxu@hotmail.com]

Re: C# Calling Executable or DLL

Thanks. The DLL contains managed C++ code. Should I stay away from
managed DLL and go with exe?


Stoitcho Goutsev (100) wrote:

DLL is contains code tha can be shared between applications where on the
other hand the exe (application) uses dlls and don't expose any
functionaluty for the others to reuse. I say usually because it doesn't have
to be like this. There are several different ways for an exe to expose
functionality for reuse, but they come with a cost.
>
My advice is to use DLLs that what they are for.
>
>
--
HTH
Stoitcho Goutsev (100)

[guxu@hotmail.com]

Re: C# Calling Executable or DLL

Thanks. The DLL contains managed C++ code. Should I stay away from
managed DLL and go with exe? Any known problem for using managed DLL? I
am still new to this.


Stoitcho Goutsev (100) wrote:

DLL is contains code tha can be shared between applications where on the
other hand the exe (application) uses dlls and don't expose any
functionaluty for the others to reuse. I say usually because it doesn't have
to be like this. There are several different ways for an exe to expose
functionality for reuse, but they come with a cost.
>
My advice is to use DLLs that what they are for.
>
>
--
HTH
Stoitcho Goutsev (100)

[Stoitcho Goutsev \(100\)]

Re: C# Calling Executable or DLL

What you are going to do with an exe. What your is that you want to do
actually?


--
Stoitcho Goutsev (100)

<guxu@hotmail.c omwrote in message
news:1161098983 .509377.196380@ i42g2000cwa.goo glegroups.com.. .

Thanks. The DLL contains managed C++ code. Should I stay away from
managed DLL and go with exe?
>
>
Stoitcho Goutsev (100) wrote:

>DLL is contains code tha can be shared between applications where on the
>other hand the exe (application) uses dlls and don't expose any
>functionalut y for the others to reuse. I say usually because it doesn't
>have
>to be like this. There are several different ways for an exe to expose
>functionalit y for reuse, but they come with a cost.
>>
>My advice is to use DLLs that what they are for.
>>
>>
>--
>HTH
>Stoitcho Goutsev (100)

>

[Adityanand Pasumarthi]

Re: C# Calling Executable or DLL

Hi,

If you use a DLL, either managed or unmanaged, it runs in the same process
as your C# executable.

In case you are using a managed C++ based DLL, you can directly refer to
that DLL and use the classes and events from your classes in your C#
application.

Lastly your requirement is not clear, so if the above points do not clarify
your doubts, then please provide your requirement in detail and I'll try to
answer your queries.

--
Regards,
Aditya.P

"guxu@hotmail.c om" wrote:

Thanks. The DLL contains managed C++ code. Should I stay away from
managed DLL and go with exe? Any known problem for using managed DLL? I
am still new to this.
>
>
Stoitcho Goutsev (100) wrote:

DLL is contains code tha can be shared between applications where on the
other hand the exe (application) uses dlls and don't expose any
functionaluty for the others to reuse. I say usually because it doesn't have
to be like this. There are several different ways for an exe to expose
functionality for reuse, but they come with a cost.

My advice is to use DLLs that what they are for.


--
HTH
Stoitcho Goutsev (100)

>
>