Question

That’s what I wanna achieve :

There will be dll which contains only methods which calls my actual methods from my application and I can share that dll with outside world regardless of which methods it includes because actual methods will be in the dll in my application but if some one uses that outside dll he/she can manages to get my application to do something in limits of I desire.

I hope I could describe what I want. I don’t know if you have ever used Skype4COM.dll. It actually works like that, it somehow connects to Skype Client and let me call some one I want. For example :

Skype s = new Skype();
s.PlaceCall("phoneNumber");

I import Skype4COM dll in my project and when i write code like above in C#, it connects to Skype and make a call.

I think there is no actual methods which makes calls in Skype4Com.dll. I think it only does have some sort of methods which reach actual methods in Skype API and make the call so whatever the developers change in Skype, it doesn’t affect Skype4Com.dll wrapper as long as signature stays the same.

So, that’s what I want to achive, I am not quite interested in writing wrappers tho, that was a sample case, I want to write a dll which reachs my API and uses method signatures and let people use the application from outside so as long as the signatures stay same, if I want to change something between block I don’t need to change the dll given out to outside..

Thank in advance….

Answer 1

If I understand you correctly, you want to expose a limited subset of the functions of your application to outside users. In effect, you want to offer a service, but nothing else.

Then you should use Windows Communication Foundation to host a service inside of your application (or elsewhere). This service could use industry-standard protocols like SOAP; or could use REST; or it could use faster binary transfers over TCP/IP for your .NET clients.

It’s perfect for a service-oriented situation like yours.