Assembly Version for CLI Based Monitor

[Christopher]

We are calling a .Net assembly through CLI from a C++ application. The .Net assembly has Analytics integrated, but always gets a version of 1.0.0.0, regardless of the version of the actual assembly. Can anyone help us set the version correctly so that we can track it properly in Analytics?

Thanks,
Chris

[[e-mail]]

Hello,

Are you manually supplying a version number to the monitor or are you letting the monitor handle this? The monitor uses GetEntryAssembly or GetCallingAssembly to retrieve the version number. So in your case the immediate caller has version 1.0.0.0. Could there be more than one assembly in the call chain?

Regards,
[e-mail]
Telerik

 

 

[Christopher]

I couldn't find a mechanism to manually provide a version number to the .NET based version of Analytics? Providing it manually would work fine if we can?

We have a C++/MFC application calling a C++/CLI DLL calling a C#/.NET assembly with the Analytics incorporated. All 3 assemblies have set version numbers, but Analytics is still getting 1.0.0.0.

Thanks,
Chris

[[e-mail]]

Hi Chris

Instead of passing in a productkey to the create method you can pass a settings object. Take a look here and here.

It is very odd that you keep getting 1.0.0.0. To debug this you could try to create dummy assembly call it from the same place and inside it call GetEntryAssembly and GetCallingAssembly and see what results you get.

I hope this helps.

Regards,
[e-mail]
Telerik