You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question about the methods available for hot-reloading managed DLL files.
This library only supports hot-reload by loading assembly files in memory through a FileStream. Is the only reason locks cannot be used the fact that a loaded assembly cannot be removed from disk, thus making it not possible for the "changed" event to happen regarding the FileWatcher? Or are there more complications making it not possible/feasible? Locks in this case referring to the loading methods where "load-by-name" or path is used (not file stream).
The text was updated successfully, but these errors were encountered:
I have a question about the methods available for hot-reloading managed DLL files.
This library only supports hot-reload by loading assembly files in memory through a FileStream. Is the only reason locks cannot be used the fact that a loaded assembly cannot be removed from disk, thus making it not possible for the "changed" event to happen regarding the FileWatcher? Or are there more complications making it not possible/feasible? Locks in this case referring to the loading methods where "load-by-name" or path is used (not file stream).
The text was updated successfully, but these errors were encountered: