Do you not have a change management process?
I an somewhat horrified that you have not:
You give the impression that you think it is just a matter of someone (end users?) upgrading their browser but in fact it is a matter of rebuilding a Windows application to use a completely different set of browser classes, with different, non-equivalent properties and methods. It all has to happen within the software and the classes it uses. Replacing IE with Edge on the outside does nothing to solve the problem.
Most people selling Windows software, like us and many of your add-in developers, would need to go through a process of:
1. Modifying code and testing it
2. Regression testing to ensure that the changes did not break something else
3. Updating the deployment package to ensure all the necessary addins get in
4. Testing the build install package
5. Updating to a web site
6. Notifying end users that they really do need to upgrade
This does not happen over a weekend. Also finding out that it needs to be addressed because one of our users raised the issue with us, probably about a week after you did it does not help.
We cannot take on new users so no new customers, no license sales until this is fixed.
Well said eJulia . Another point to make is that not all developers use dotnet (strange but true...), so in our case we cannot benefit from the amazingly generous contributions of other dotnet devs.
I have a theory (based on the new access code starting "ory_") that MYOB has taken on an "IAM" program from www.ory.sh, to handle the authorisation part of the API. Possibly it was expected (or the advice was) that the change would be transparent to all add-on programs. I await confirmation.
