October 13, 2015
This release fixes an migration issue introduced in .NET monitors 3.3.25: a change in digital certificate had the unexpected side-effect of causing the monitor to report upgrades as "new installations". The effect would be that the number of "new installations" reported would be too high.
An example:
A customer app version 1.1 was released with a monitor prior to 3.3.25, e.g. 3.2.61. The customer then releases version 1.2 using the monitor 3.3.25. This will cause all upgrading users to wrongly be reported as "new installations".
The remedy is to upgrade to 3.3.43 and not upgrade existing applications to use 3.3.25 or later. Revisiting the scenario above, this is what would happen then:
The customer releases version 1.2 which is using the monitor 3.3.43. This monitor will recognize that the app is just being upgraded and correctly not cause it to be reported as a "new installation".