Part of our legacy desktop application included a viewing component which was developed as an ActiveX control. It was developed in VB6 and used the ActiveX flavor of GDPicture for some of its display architecture. This ActiveX control was also used by our web application for the same display functionality.
The desktop application has been rewritten in C# for our next release. This also includes a new C# version of our viewing component and this code uses the .NET flavor of GDPicture.
Our legacy web application will not be replaced within this release cycle and our planned approach was to add a set of COM interfaces to a C# wrapper that contains the new C# viewing component. These COM interfaces were developed to mirror the legacy ActiveX control and slip into our web framework.
In some preliminary testing, we're running into an issue when the C# viewing component makes the calls to RegisterKEY. In a standalone test application, they succeed. When the component is loaded as part of a web page, those calls fail.
Is the usage scenario described above, where the .NET flavor of GDPicture ends up on a web page in IE, a configuration that should function correctly?
Thanks for any information that can be provided.
GdPicture.NET is now completely incompatible with IE and ActiveX architecture, since version 11 if I remember well.
We are now offering an extension, DocuVieware, to offer smooth consumption of GdPicture features through any operating system and browser.
Please let me know if you need further information.
With best regards,
Who is online
Users browsing this forum: No registered users and 3 guests