Is it possible to build a loadable extension with the newest Slicer version, i.e., 4.13, and install it in an older slicer version, i.e., 4.11?
No, as a general rule everything needs to match exactly for a loadable module to work (compiler, OS, code version…). This is a C++ thing, not specific to Slicer.
Thanks for the reply. I created a .zip via cpack of a pure python based extension developed with Slicer 4.13. But I am still not able to install the .zip file in Slicer 4.11. Is there something I need to be aware of when trying to install a python extension in an older version, or should it work out of the box?
If it’s pure python it should work across versions since 4.11 and 4.13 are pretty similar, but you can look in the error log and the python console for any message to indicate something going wrong.
If it’s just python scripted modules you can also put them in a directory and use the Edit->Application Settings-> Modules panel to add a path to that directory and they should be discovered when you start slicer.
The Major.Minor version number is used to generate subfolder name within the zip file to prevent using incompatible packages. If you are sure that the scripts work in both Slicer-4.11 then rename all the
Slicer-4.13 folders in the zip file to