Rider is running/debugging an old build Follow
You have made some changes but Rider sticks to an old build? First of all, have a look at your Run/Debug Configuration and make sure that "Build project before run" is added to the list of actions to be performed before the launch:
In case it is there then please let us know about the problem. Here are the troubleshooting steps:
1. Go to 'Rider -> Settings/Preferences -> Build, Execution, Deployment -> Toolset and Build'.
2. Check which MSBuild version is used. Does it lays in .Net SDK or in Visual Studio folder?
3. Is "Use ReSharper build" checkbox turned on?
4. Turn on "Write log to file" checkbox and choose "Normal" verbosity. IMPORTANT: don't forget to turn off this checkbox when you collect all the logs.
5. Close Settings dialog.
6. In case you are on Mac/Linux then check your Mono version.
7. In case you have .Net Core project then check your .Net Core version.
8. Make some changes in the code and run your project.
9. Make some changes in the code again and build solution via the menu on the top.
10. Make some changes in the code one more time and build selected project via Solution Explorer.
11. Go to 'Help -> Show Log in Explorer/Finder/File Manager'.
12. Zip all the log files in the folder and attach it to Support request or Youtrack ticket.
13. Turn off "Write log to file" checkbox (see step 2).
That is it - we will analyze the log files and see why the project doesn't run correctly. Thank you for your cooperation!
Please sign in to leave a comment.
I guess more people are having issue with this since the answer was updated yesterday? Do you have an youtrack issue tracking this opened?
Currently, "Use Resharper Build" 's default value is "true", but it has to be set "false", in my opinion.
Because "Resharper Build" is not reliable that much yet.
Especially, dependent projects' modification is not tracked correctly.
the same issue with the debugger, very annoying
even build of the project with changes sometimes can be useless, and you need to rebuild all project dependencies...
I have the same problem.
It doesn't work well even for a Console project with one dependent Library project.
In my feeling it becomes buggy starting from JetBrains Rider 2020.1.3 Build #RD-201.7846.1, built on May 15, 2020 version and/or .NET Core 3.1.
But as soon as I turn "Run ReSharper Build" setting OFF - everything start working as expected.
I've also started experiencing this issue recently.
Setup:
ProjectA
ProjectB (depends on ProjectA).
1. Configure default run of ProjectB.
This results in:
2. Make a change in ProjectA, click Run or Debug, build output shows ProjectA being rebuilt, but not ProjectB , hence project artifacts are not copied.
Sometimes it does rebuild ProjectB, so the occurrence seems a bit random.
Not sure how related this is, but this is the best place I've found after much Googling.
I have what looks to be the same issue, but when using Resharper as part of Visual Studio.
I've enabled Resharper Build and if I just hit Debug > Start then it will correctly build whatever projects require building, but then doesn't use the artifacts produced for the debugging session. I've verified this by adding / removing various statements and that no breakpoints are hit because the executing code is different from the source.
Visual Studio 2019 Professional, 16.7.2
Resharper 2020.2.1
When I run a project (using F5) it seems to build dependencies, but not the program project itself, so it basically runs the old .exe using the new .dlls. (or something? now that I think of it, would that even cause this problem? maybe it doesn't copy the dlls?)
I can see it say "building <library>" but then says "build complete" without ever having said "built <program>"
It's annoying because your feedback loop of <make a change>, <test change>, <make another change>, etc. breaks down when you're really running the last version of the code, not the new version.
I notice that this happens even if I specifically choose to build the project, not just press F5. In my case I have made changes to a transitive dependency, and not to the project being built.