I’ve made .dlx extension for my script and load it with LoadDllsFromDir.
It loads and works perfectly, and now I’m making installer/uninstaller script that should copy/delete all script/icons/dlx files.
My problem is that some 3dsMax versions (2013 for example) locks dlx file and I can’t delete it in uninstall procedure. I thought that 3dsMax should lock all loaded dll files, but 2016 and 2019 don’t. In 2016 and 2019 I can easily delete dlx and uninstall script.
I understand that dlx is still in RAM while 3dsmax is running. My task is to make reliable uninstaller for script that will kill this dlx file.
Why 2013 locks file, but 2016 and 2019 don’t? Is it some kind of deprecated feature of 3dsmax?
Can I force 3dsmax 2013 (and other versions that lock dll) to unlock these files so I can delete them? I don’t need to “unload” dlx functions, I just want to kill a file.
Should I worry about killing loaded dlx file if I can do that? I have 2 functions in this dlx, both of them work after file delete, but I don’t need them after script uninstall anyway. I mean, may 3dsmax become unstable after such actions?