Strongly Typed .Net 2.0 Interop for ActiveX Pro v2016.0.0.2

[Yokogawa Marex]

We have just upgraded from TeeChart ActiveX v5 to v2016.0.0.2 in order to produce a patch of our software (asp.net .net 2.0 Website) to resolve a customer issue where Japanese text was not being displayed correctly, this was fixed in a v2013 version of TeeCharts.

Because we are only producing a patch not a full release we are restricted as to what we can change.
Project constraints:
Visual Studio 2008
All assemblies compiled against .Net 2.0 x86


The Teechart upgrade went fine and fixed the original issue, but during the patch testing we have identified an issue with the way the Strongly Typed TeeChart Interop was generated.

When attempting to create a gantt chart we got an application error with the following information:
“Exception: System.MissingMethodException
Message: Method not found: 'Void System.Threading.Monitor.Enter(System.Object, Boolean ByRef)'.
StackTrace: at TeeChart.ITChartEvents_EventProvider.Finalize()”

I have verified that the method ‘System.Threading.Monitor.Enter’ has only been available from .Net 4.0 onwards.
The Strongly Typed interop (TeeChart.dll) we are using was provided with the release from the following folder:
‘<ProgramFiles>\Steema Software\TeeChart Pro v2016 ActiveX Control\Utilities\Vs.net\Strong Named DLLs\’

As the documentation on the interop doesn’t explicitly state I can only assume that the interop was generated using .Net 4.0.
If you refer back to our project constraints this causes a problem because we can only use .Net 2.0, and it’s not possible to reference a .Net 4.0 dll from within an application domain that is running .Net 2.0.

Request: Is it possible for you to generate a Strongly Typed Interop for ActiveX Pro v2016.0.0.2 that targets .Net 2.0 that we can use.
(In future releases could you also update the documentation to indicate the .Net framework that the interop targets, including a .Net 2.0 and a 4.0 version of the interop would be even better.)

[Marc]

Hello,

We'll take a look to preparing the version you require. It seems likely that we'll need to use the older versión of Visual Studio (VS2008 or earlier) to target the framework correctly.

Regards,
Marc Meumann

[Yokogawa Marex]

Many thanks.
It would be great if we could get something by the end of Tuesday next week.

[Yokogawa Marex]

Hi, Just wondering if you have made any progress generating a .Net 2.0 Strongly Typed Interop for ActiveX Pro v2016.0.0.2

[Yokogawa Marex]

Has any progress be made in generating a .Net 2.0 Strongly Typed Interop.
We could possibly work with a .Net 3.0 – 3.5 SP1 Strongly Typed Interop if that’s the only other alternative.

Is there any way we can generate the Strongly Typed Interop ourselves, but I believe it would require access to the key file, which is not distributed with the install for obvious reasons?

Unfortunately we have no option but to use Strongly Typed Interops because it needs to be added to the GAC.

[Sandra]

Hello,
I have sent an email with the Strong Names dlls for .net framework 2.0.

Hoping this helps

Thanks in advance

[Yokogawa Marex]

Hi, Thanks for your reply.
Unfortunately, we haven’t been able to find the email yet, please could you resend it.
Is there also an option for me to private message you the details of an alternative email address, if it still doesn’t get through.
Many thanks

[Yeray]

Hello,

Please send a mail to "info at steema dot com" asking for the files. Please add a reference to this thread.

[Yokogawa Marex]

Just to let you know that I have done some initial testing and the new interop you provided build against .Net 2.0 have fixed the issue we were seeing.

Many Thanks

[Yeray]

Hi,

Just to let you know that I have done some initial testing and the new interop you provided build against .Net 2.0 have fixed the issue we were seeing.

I'm glad to hear that!