12-15-2021, 05:08 PM
Hello there.
I have figured out how to compile an assembly .dll file with a bunch of common class methods that I reuse often and share with my team. That's much more efficient than trying to replicate individual class files. However, I noticed that once I compile and use the assembly once it seems to get cached. If I make changes to that class and re-compile the .dll file, I get runtime compile/link errors when trying to run a script referencing that .dll until I exit Autepad and re-launch the UI.
Is there a way to do something similar to flushing module/library cache? I'm thinking similar things happen occasionally on linux and I'd run something like a ldconfig to rebuild the shared library cache.
It's not the end of the world to exit/re-launch, but if I'm debugging something and re-compiling it's a bit of a pain. Ideally though and in normal operation that library isn't changing very often.
I have figured out how to compile an assembly .dll file with a bunch of common class methods that I reuse often and share with my team. That's much more efficient than trying to replicate individual class files. However, I noticed that once I compile and use the assembly once it seems to get cached. If I make changes to that class and re-compile the .dll file, I get runtime compile/link errors when trying to run a script referencing that .dll until I exit Autepad and re-launch the UI.
Is there a way to do something similar to flushing module/library cache? I'm thinking similar things happen occasionally on linux and I'd run something like a ldconfig to rebuild the shared library cache.
It's not the end of the world to exit/re-launch, but if I'm debugging something and re-compiling it's a bit of a pain. Ideally though and in normal operation that library isn't changing very often.