7 replies
by terry.bobo Accepted solution
by tony hopkinson Accepted solution
If you are going service based you expose entry points onto the dll as operations in the web service. All it is basically is an abstraction of an RPC call.
If you want to to access a dll with a .net component, you are entering unmanaged execution and a lot of difficulties.
Look up .NET interoperability, safehandle and intptr.
by terry.bobo Accepted solution
by tony hopkinson Accepted solution
You need some process to host the dll on the application server.
If you were to use ASP.NET and make it aware of the location of the dll you could access it through there but then the application dll would be loaded into the web server. One suspects that isn't what you wish to achieve.
On that basis you need an application to sit on the application server that loads the dll and provides an interface to it.
by dkehring Accepted solution
by tony hopkinson Accepted solution
That's exactly what MS have done with Windows Communication Foundation (WCF).
Well it's not strange really, an obvious way to go.
by onbliss Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending