Rider remembers renamed .dll files


I was faced with the fact that when renaming a .dll file in runtime, the Rider 2019.3.2 after renaming connects this .dll file. Renaming occurs before the first use of the .dll file, so the .dll file should not have been downloaded anywhere before renaming.
A similar situation in the Visual Studio 2019 leads to an FileNotFoundException.

Is this expected behavior or error in Rider?

Thanks in advance.

1 comment
Comment actions Permalink

Hello Dmitry,

Would it be possible to provide a bit more details on how exactly you are renaming dlls in runtime and how it results in Rider? It would help a lot if you could provide a screencast demonstrating the process and upload it with a new issue on our bug tracker. Thank you in advance!


Please sign in to leave a comment.