Newsletter Issue 4th Quarter 2018
We've worked with several AVR Classic customers lately helping them resolve challenges with their legacy Classic apps. During this work, we've come to the opinion that integrating AVR for .NET with AVR Classic is not only a great way to solve AVR Classic-imposed challenges and limitations, but it's also a way to start replacing parts of your AVR Classic applications with AVR for .NET. Many AVR Classic applications are quite large and complex and rewriting them from the ground up isn't doable--at least quickly. But over time, incrementally replacing parts of them with AVR for .NET may be the key to clawing your way out of COM prison. This article provides the keys for integrating AVR for .NET with AVR Classic.
We know that planning for AVR upgrades isn't a fun thing to put on your to-do list. ASNA has made a substantial investment in AVR 5.0 and this version buys time for your AVR Classic applications. Old AVR Classic code would probably run forever on the environments for which it was intended. But those environments (primarily Windows XP) are no longer in service. To ensure your AVR Classic apps work appropriately on newer versions of Windows an AVR 5.0, upgrading is a must.