Migrate SDK 3.5 from x86 to x64

I have a CSharp dotnet application that uses VideoOS SDK 3.5 .

I am in the process of converting the project from x86 to x64. When runnnig and try to create an ImageViewerControl, a get an error “Class not registered”.

Using the Milestone dependency tool, I see that VideoOS.SDK.dll is AnyCPU, but ImageVIewerDotNet.dll is x86 .

Is there an x64 version of the 3.5 SDK?

Should I be able to use the 3.5 SDK in an x64 application? What needs to be done to transition?

I am also integrating the latest VideoOS SDK (nuget) for an alternative way to view video. Is there any reason the new viewer would not work with a very old XProtect server? The answer may be to remove the old 3.5 ImageViewerControl from my application and use the new SDK only.

VideoOS SDK 3.5 was released July 2010. It is purely 32 bit. Note that the activeX used in SDK 3.5, is out of support, it was discontinued as a component in MIP SDK 2018R3.

As you can imagine a lot is now different.

A new MIP SDK can work with older XProtect sites and servers. If the old VMS is e-code, which it will be if the VMS is also that old, we cannot recommend the newest MIP SDK. Read about it here: https://developer.milestonesys.com/s/article/newest-MIP-SDK-for-XProtect-Professional-VMS-E-code

I am divided between wishing that our customers would be quicker to adapt our newer technology in our newer versions and thinking how cool it is that systems and integrations have a really long life span.

Out of curiosity; what is the product and version of the XProtect you are working with?

Thank you for your response.

I do not often have access to our customer site. I have a copy of quote from Advanced Network Systems, 1/21/2013.

It appears that XProtect Enterprise 7.x was purchased. So according to the link you referenced, it is an E-code product and I should use 2019R2 x64 SDK. Note that we are using the system to record and distribute video. There is no camera control.

Our customer is wanting to update the XProtect system, both software and hardware. A priority is to make use of h.265 video.

Robert Otto | Trident Systems Incorporated

Principal Systems Engineer, Integrated Systems Engineering Group

Thank you, you satisfied my curiosity.

I think our mutual customer will realize that they get so much more than H.265 when they decide to update. :slight_smile: