Hello,
I have created a web service which is using a VB6 DLL the same DLL is being used by other application also, So it changes many times. But because of this I have to build my web service each time with new reference. Can any one please suggest me the solution for this, So I can create a wrapper or something like that which will take care of the new DLL and I need not to rebuild it.
Thanks in advance...

__________________
No WAY is good until you know your DESTINATION

.NET already creates a wrapper to access the COM dll, the Runtime Callable Wrapper assembly. This assembly is the actual assembly referenced by your web service project and is the one you need to rebuild. If you configure your COM dll to use binary compatibility you might be able to update the COM dll without needing to update the wrapper. I've done this in the past. However, if you change any of the interfaces of the classes in the COM dll you'll be forced to update the wrapper. You might want to look into automating the process of building the wrapper and web application.

-Peter

Hi Peter,
Thanks for reply. But I talked to the person responsible for making new dll. Each time he changes the dll he change name also e.g. DLLNAME_Date.dll.
So in this condition I think building web service each time is essential. Could you please suggest something?

I have used the NAnt build/scripting tool for lots of tasks. This might prove useful for you. It can run the interop generator program (tlbimp.exe) to create interop assemblies. You can also use it to build applications. You could use that to rebuild your web service application whenever there's an update to the COM dll.

-Peter