I have made a simple web service in Visual Web Developer 2005 Express Edition Beta. It runs ok when testing it from the development environment runing on the web server that comes with the VWD. But when runing the service from IIS 5.1 with .NET framework 2 Beta installed I always get an error when calling the COM object. I created a virtual directory in the IIS refering the directory made by the VWD and have a refence to the COM in the form of Interop.objectname.dll in the Bin directory.

What am I doing wrong or not doing right when running from IIS?

Thanks in advance,
Kristinn

I am not sure why you are calling COM objects. After all, you've created a Web Service, right? What do you need COM for?

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Actually I should have called it an ActiveX as that is what it is. I'm using the web service to communicate with an older software that has an ActiveX to comunicate over the internal network. When it works, like when it's run in the Visual Web Deweloper environment, it's quite simple to use and saves a lot of programming.

I'm wondering if the calls to the ActiveX works from the development environment shouldn't it also work from the standalone web service (when the code has been moved to the IIS server)? Are there som setings I need to do manually?

Kristinn

I don't think I understand the problem. Can you provide more detail about your setup?

What talks to what and how? Can you show us some code? And did you register the Active X dll (I assume it's a DLL) on the other server?

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to: You Don't by Tricky (Track 10 from the album: Maxinquaye) What's This?