i have an activex dll.
Allow me to explain the whole picture here, I have an API developed for Windows environment that integrates with a third-party camera drivers, of which I have a 32 bit version and a 64 bit version... both work well on desktop environments without any problem. Recently, I was asked to export my API for web access so that people can integrate my API with their web pages just like they do on desktop applications to call my camera, basically a Web API
I'm no expert in web so I did my research, and with the limited information I have, I found a way to expose my API by registering the assembly of an exposed dll that I created using the .Net regasm tool. This worked fine on 32 bit machines with one setback: I had to Enable the "Initialize and script ActiveX controls not marked as safe for scripting" from IE options, but now when I tried to do the same thing on a 64 bit machine, it didn't work. I used the 64 bit regasm tool this time just like I'm suppose to do, and I was able to register successfully using the same command "regasm mydll.dll /register /codebase /tlb"
Now when I try to initiate the call to my API through JavaScript such as
var myAx = new ActiveXObject("MyAPI.WebInterface");
I keep getting the error message "Automation server can't create object" even though my settings are the same as the 32 bit machine and I used the 64 bit IE here. I tried using my 32 bit version of the API on the 64 bit machine after registering it correctly of course, and I managed to get passed that point, but my 32 bit API cannot call the 64 bit camera driver, so it wont do for this case.
Is there any specific command I need to add in order to register correctly on 64 bit machines? Is this the right way to expose my API for web use?? and is there a way I can support all browsers at the same time, noting that this only works on IE?? please advice