If I create a reference to the DirectShow COM DLL (or any other non .NET DLL) and send it out to clients, will they need this dll installed ? or will the reference make a copy of it in the .exe and carry it around without the .dll file ?
If I create a reference to the DirectShow COM DLL (or any other non .NET DLL) and send it out to clients, will they need this dll installed ? or will the reference make a copy of it in the .exe and carry it around without the .dll file ?
In case of DirectX they will definetly need the whole DirectX installed. And while we are at it, have a look at DX9, it has a very nice manageg C++ and C# interface.
hth
-nv
She was so Blonde, she spent 20 minutes looking at the orange juice can because it said "Concentrate."
When in doubt, read the FAQ.
Then ask a smart question.
ok I'll check it out.
but
What about other Non dot net / Non Direct X DLL's ?
The client will need a copy of it. Your executable will only have a reference to it. You might find an installer that checks all those dependencies and includes the dlls in your setup, but I'm not sure if the inbuild installer will do this.
hth
-nv
She was so Blonde, she spent 20 minutes looking at the orange juice can because it said "Concentrate."
When in doubt, read the FAQ.
Then ask a smart question.
What about Crystal reports ? with the end user need something installed or will the framework runtime cover that ?
what if it's crystal reports over asp.net ?
If it's ASP.NET then it is Server-Side executed and generates HTML - nothing extra is needed.
My Avatar says: "Stay in School"
Rocco is the Boy!
"SHUT YOUR LIPS..."