Can we reliably test frameworkversion for conditional compile Cancel The title field is required!

1. Carl Verbiest

   

   59 posts
   Registered:
   12 Oct 2018
   24 Apr 2020

   Link to this post

   I'm looking for an equivalent of conditional compile based on {&proversion} but for SCL version.
   
   Is the following construction reliable ?
   Is there a better alternative ?
   
   &if "{Consultingwerk/frameworkversion.i}" gt "Release 11.3 #57173@2020-02-10 UTF-8"
   &then
   message "{Consultingwerk/frameworkversion.i} is greater"
   &else
   message "{Consultingwerk/frameworkversion.i} is NOT greater"
   &endif
   
   

   Background
   

   We switched from framework version Release 11.3 #57173@2020-02-10 UTF-8 to Release 11.3 #58494@2020-04-22 UTF-8.
   
   Because of the addition of CustomParameter in DatasetModelPerformer we need to change our logic for setting the FetchDataRequest:CustomParameter.
   
   I want to use conditional compilation because we want to be able to use our tool version with both SCL frameworkversions.
   
2. Mike Fechner

   

   319 posts
   Registered:
   14 Sep 2016
   24 Apr 2020 in reply to Carl Verbiest

   Link to this post

   I would not count on that ... Alpha-Comparison of numeric values ... (in a few years we will hit 100000)
   
   We don't have plans per se to change the release numbering. But as of today, I would also not say never either. We do have customers asking for a more predictable numbering of future releases (maybe 2020.11 for the 11th release in the year).
   
   We are in the process of planning LTS releases for the SmartComponent Library - and that might have impact on the version numbering as well. The demand to synchronize ABL (backend) and  TypeScript (frontend) version numbers is also a factor.
   
   We will be upgrading the release environment to OpenEdge 11.7 in the near future. That will change the first bits of the version number - which should not bite you in this case. But it might be worth mentioning this. 
   
   To be on the safe side, I would suggest you add a custom value like a feature-toggle in a file like products.i