Rider + DockerCompose Proj, how to relaunch.
I am trying to use Rider with a solution that has a DockerCompose.proj, and I am running into an issue where I can launch the application (it has many services), and the first launch works great, and is pretty quick (way faster than in visual studio).
However, if I make a code change, in order to see that change, I have to stop the container, then re-launch. What I would like to do, similar to how it works in visual studio, is just hit the launch button again. The alt, stopping the container, isn't the end of the world, but I have to remember which services need to be updated, manually find them, kill them, then relaunch. Just hitting launch, would be a lot easier.
Does anyone work with a DockerCompose.proj and have any suggestions for workflows?
Please sign in to leave a comment.
Someone needs to study, why it is when you spend days researching an issue, then finally create a question on a forum, you seem to find the answer…
Had to add “Build: Always”, I wish it would detect the images that need to be rebuilt. But hey, it works. It makes it slower, but overall better. Still, if anyone else has any tips, please chime in.
Hello,
Thank you for contacting Rider support and for sharing your experience. I am glad to hear that a solution was found.
Meantime, I submitted this issue to our tracker, so that a developer might consider bringing improvements here in the future: RIDER-120684 Rider doesn't detect changes on dockercompose.proj run
Have a nice day!
Thanks Dmitry