Rider cannot always publish my dll due to "550 The process cannot access the file because it is being used by another process."
Answered
I publish to my own Windows Server server with IIS using the publish option in Rider.
This work great! But not all the time.
I often get this error:
Publish to custom server failed: failed to transfer file '....dll': cant open output connection for file .... Reason: "550 The process cannot access the file because it is being used by another process. "
To solve this I need to log in into my server. Stop the Webapp in IIS, do the publish again and restart the Webapp. This is very cumbersome.
Is their another way to do this using Rider?
Please sign in to leave a comment.
Hello,
Could you, please, next time when you meet this problem define what process locks files using Process Explorer tool, for example? Also, we'd like to know what command line the process was run with, and what is its parent process. Please use the latest EAP build while doing so.
Thank you!
I'm experiencing this problem too. This happens is when I deploy a web app. IIS is the process using the file. If I stop my IIS website, then deploy, it works, then I restart the IIS website. But I hate having to stop IIS every time I want to deploy an update. Do you have any suggestions?
Please take a look at this comment on the corresponding feature request: https://youtrack.jetbrains.com/issue/RIDER-40512#focus=Comments-27-4008444.0-0
In short: please use `Restart` button on the toolbar for now, we're hoping add feature to do it automatically in future versions.