There have been several reports of a problem with the addin not working so the addin will prompt when the issue is encountered. To get a better feel for how widespread the issue is the addin can request a page on the site to track the number of users and how often the issue is encountered.
The first time the issue occurs the addin will generate a (per user) GUID to uniquely identify the user. This GUID is used to increment the per user error count. No other information is sent.
I'm not a big fan of software that has anything that tracks usage, but if the issue effects a large enough group (and I can demonstrate that) it is much more likely to be addressed by Microsoft.
I'd like to keep the Early Access process very short (a few days) this time around so please if you're in the EA group try it out and let me know if you have any issues.
- write AlwaysUseFPD key
- use invariant culture to format current position
- prompt user if the CurrentExperience object is null (i.e. MC is broken) and option to notify me
bin | source