Quantcast
Channel: Silk Performer
Viewing all articles
Browse latest Browse all 4084

Forum Post: SilkPerformer 17.0 upgrading caveats

$
0
0
It could be just me, but in the past, agent machines played more nicely with different versions of SilkPerformer, as in version 16.0 agents coexisted and did not step on agents version 16.5. With the latest release of SilkPerformer version 17.0, however, version 17.0 agents stepped on version 16.5 agents, and vice versa - at least in our case here.  So rather than run 60 or 90 days with version 17.0 and 16.5 together for backwards compatibility, we removed 16.5 completely. This now begs the question, if you want to get an older version 16.0 or 16.5 script, is it acceptable to cut and paste the older .bdf file into a new script created in v. 17.0 workbench?  Or should one go to the trouble of getting the previous workbench version (16.5, 16.0, 15.5, 15.0, etc.) and export the project because of underlying dependencies? I'm hoping cut and paste is OK ....

Viewing all articles
Browse latest Browse all 4084

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>