Date/Time: Wed, 07 Dec 2022 05:55:24 +0000
Post From: v2195 recompilation...
|@sstfrederik - Posts: 385|
We think that what we need to do is to support any version number in a SC DLL file name. It would indicate the version it is compatible with, up until infinity if there is no other DLL (with the name the same aside from the version number) with a newer version number, or compatibility up to a DLL with a newer version number.
Will filenames without a version number have precedence in this solution? When do you think this will be implemented?
Naming the study file with a version should be optional in my opinion.
Just looking to offer updates on studies from a filename without a version number.
The _2151_ arrangement makes this not possible and I need to upload multiple versions.
If from a certain SC version the dll without a version number can take precedence over the _2151_ filename I can phase out the autodownload of that _2151_ and do not need to make things to difficult managing all these different files.