Hi,
We are trying to use the Telerik controls for development of applications that can integration into SAP Business One. In order to do that, we wanted to use the control into an ActiveX object, and then use that object inside of the SAP SDK on custom forms. We have been able to get the Telerik control into an ActiveX DLL, the use that DLL on a Windows form.
However, when we try to use the same ActiveX DLL inside of the SAP System and try to set the ClassID property of the SAP SDK ActiveX object, which requires the ProgID or GUID of the ActiveX object, and pass the reference, the .NET program is throwing an exception.
If anyone has taken this approach with a Telerik control (through an ActiveX DLL) in an environment like SAP Business One, and can assist in what could be causing this issue, please post any pertinent information.
Thanks.
We are trying to use the Telerik controls for development of applications that can integration into SAP Business One. In order to do that, we wanted to use the control into an ActiveX object, and then use that object inside of the SAP SDK on custom forms. We have been able to get the Telerik control into an ActiveX DLL, the use that DLL on a Windows form.
However, when we try to use the same ActiveX DLL inside of the SAP System and try to set the ClassID property of the SAP SDK ActiveX object, which requires the ProgID or GUID of the ActiveX object, and pass the reference, the .NET program is throwing an exception.
If anyone has taken this approach with a Telerik control (through an ActiveX DLL) in an environment like SAP Business One, and can assist in what could be causing this issue, please post any pertinent information.
Thanks.
1 Answer, 1 is accepted
0
Hello Gopal Viswanathan,
We have seen similar error report only once so far -- it was about the Microsoft Interop Forms Toolkit 2.0 (third-party toolkit that is not part of the .NET framework and that is generally unsupported by us for that reason) -- the customer tried to load WPF content with telerik chart in VB6 application and the application was crashing with this error (the same chart setup worked seamlessly in a native WPF application, as well as hosted within ElementHost in a WinForms application).
The solution that resolved the Interop Forms Toolkit scenario was to manually add reference to the Telerik.Windows.Controls.Charting assembly. Alternatively, you can use the AppDomain.AssemblyResolve event that occurs when the resolution of an assembly fails. You can find more information here, here, and here.
Hope this helps.
Sincerely yours,
Manuel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
We have seen similar error report only once so far -- it was about the Microsoft Interop Forms Toolkit 2.0 (third-party toolkit that is not part of the .NET framework and that is generally unsupported by us for that reason) -- the customer tried to load WPF content with telerik chart in VB6 application and the application was crashing with this error (the same chart setup worked seamlessly in a native WPF application, as well as hosted within ElementHost in a WinForms application).
The solution that resolved the Interop Forms Toolkit scenario was to manually add reference to the Telerik.Windows.Controls.Charting assembly. Alternatively, you can use the AppDomain.AssemblyResolve event that occurs when the resolution of an assembly fails. You can find more information here, here, and here.
Hope this helps.
Sincerely yours,
Manuel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.