static library in c# library control

[Guest]

I'm new to using c#, but what I'm trying to do is create a library control
containing a form which in turn contains a Windows application that I have
defined in another library.

I'm able to do it if my application which I put in the form is a c++ dll
like so:

[DllImport ("C:\\MyApp.dll")]
private extern static void RunMyApp(IntPtr handle);

private void InitializeComponent()
{
this.Name = "MyControl";
this.Size = new System.Drawing.Size(480, 640);
RunMyApp( this.Handle);

}

However, my requirements now dictate that the application I want to put in
this form is contained in a static c++ library. I have not been able to
import the static library into the control. This is literally the only
function that I need to call from my static library application. Is there a
way to do this?

 

[Dmytro Lapshyn [MVP]]

Hi,

To the best of my knowledge, you cannot use static C++ libraries from C#
code. What you can do however is to conjure up a very simple C++ dll
exporting just one function, and within that function you will call whatever
you need from the C++ static library. Then, use the resultant DLL from your
C# code through the regular DllImport attribute.

 

[Guest]

Thanks for the response

However, the reason I need to use a static library is because my end result
is a web application and if I were to use a .dll then the web application
expects the .dll on the users machine....

I'm now looking into an ActiveX control.

If anyone knows another way around it, then please let me know!

 

[Dmytro Lapshyn [MVP]]

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.

 

[Dmytro Lapshyn [MVP]]

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.