G
Garry Hall
Guest
As for "making a new Progress.Telerik.dll available" when Telerik brings out a new version, we did consider that, but that is a maintenance and supportability nightmare. Progress have to build Progress.Telerik.dll for all supported OpenEdge versions (at the moment, just 11.6, but then there would be 11.6.1, 11.7 etc...) for all supported Telerik versions... the matrix gets big fast, as Telerik releases versions much more frequently than OpenEdge, and OpenEdge versions stay supported a long time. Then application vendors have to provide the correct Progress.Telerik.dll required by the application. If you don't the customer will get the Exceptions instead, resulting in support calls. It is also a problem for WebClient: the application vendor would have to know which version of WebClient the end-user is running, and ship the appropriate Progress.Telerik.dll with it... although under some circumstances you might be forcing the user to the latest WebClient version, in which case you would have to deploy multiple Progress.Telerik.dll assemblies with the application, and provide logic to install the correct one. We opted to use the redirection in the app config file to address this instead. The theoretical solution I mentioned above would also avoid these problems.
Continue reading...
Continue reading...