Ah, in this scenario - yes, the DLL is required on the client :-(
Therefore, I'd either write the whole control in C++ (by using ATL for
example), or I would have to rewrite the static library in managed code.
BTW: managed Windows Forms controls require IE 6 and .NET Framework on the
client side.
BTW2: The control *might* automatically download necessary DLLs, but I am
not sure which permissions are required for it to do so. What I do remember
is that the DLL must be on the same server and most likely in the same
virtual folder. See no-touch deployment docs in MSDN for more information.
--
Sincerely,
Dmytro Lapshyn [Visual Developer - Visual C# MVP]
"newest newbie" <ne**********@discussions.microsoft.com> wrote in message
news:EF**********************************@microsof t.com...
On the user machine? Why? If the DLL is used only on the server side,
there
is absolutely no need to have it on the client.
When I use a dll in the way I first mentioned in a control library form
and
then place that control in a web application, the control looks for the
dll
on the clients machine. I'm not experienced with this topic, is there a
way
to specify that the dll is on the server?
Thanks for your help