We have recently considered several options, for example the Evergreen Runtime and Fixed Version runtime distribution options but we are yet to find one that fits our needs. Hence we are asking you for help. The current situation is that the WebView2 browser simply is not stable enough and we are trying to drop support of the old IE-based (WinForms) browser control as that one is also not stable enough and prevents us from developing newer features in our application.
Our application has several releases, ranging from a weekly/monthly in-development version to a version that is two years old. We are only able to update parts of the database of the older versions, and we cannot update the C++ and installer parts. More specifically, once a version gets released we cannot update to a newer (C#/.NET) SDK in that old version. If we were to use a Fixed Version runtime then we also are not able to update that one. If we would decide to use a Fixed Version runtime then the oldest versions would lack two years worth of bug- and security fixes, this is not acceptable to us.
Hence we decided to use the Evergreen Runtime, but fact is that Microsoft simply makes too many mistakes resulting in our application being broken on all of our versions simultaneously with no way to fix those issues by us, the only option is to wait for Microsoft to fix the problem. The result is that customers face an unstable application for at least one week on average, this is actually the current situation, and is yet again unacceptable.
So how do we ensure that we can maintain an application that is not subject to WebView2 issues?
Is it possible for Microsoft to change the way the Evergreen Runtime works such that the previous version is also always available and we can always fallback to that version from the (C#/.NET) SDK, via command line options for example?
Or do you have any other suggestions?
We have recently considered several options, for example the Evergreen Runtime and Fixed Version runtime distribution options but we are yet to find one that fits our needs. Hence we are asking you for help. The current situation is that the WebView2 browser simply is not stable enough and we are trying to drop support of the old IE-based (WinForms) browser control as that one is also not stable enough and prevents us from developing newer features in our application.
Our application has several releases, ranging from a weekly/monthly in-development version to a version that is two years old. We are only able to update parts of the database of the older versions, and we cannot update the C++ and installer parts. More specifically, once a version gets released we cannot update to a newer (C#/.NET) SDK in that old version. If we were to use a Fixed Version runtime then we also are not able to update that one. If we would decide to use a Fixed Version runtime then the oldest versions would lack two years worth of bug- and security fixes, this is not acceptable to us.
Hence we decided to use the Evergreen Runtime, but fact is that Microsoft simply makes too many mistakes resulting in our application being broken on all of our versions simultaneously with no way to fix those issues by us, the only option is to wait for Microsoft to fix the problem. The result is that customers face an unstable application for at least one week on average, this is actually the current situation, and is yet again unacceptable.
So how do we ensure that we can maintain an application that is not subject to WebView2 issues?
Is it possible for Microsoft to change the way the Evergreen Runtime works such that the previous version is also always available and we can always fallback to that version from the (C#/.NET) SDK, via command line options for example?
Or do you have any other suggestions?