3 ms·
I think it is kind of insane not to recompile when your downstream dependencies change and the recompilation fixes this problem. Like presumably it makes sense
by benmmurphy 9y ago
I think it is kind of insane not to recompile when your downstream dependencies change and the recompilation fixes this problem. Like presumably it makes sense to run your tests again when you change downstream dependencies and it is extra work to run tests independently of recompilation so I think most people's process would be update dependency -> recompile -> run tests. I just remember Java having lots of gotchas with binary compatibility and I assume C# has similar issues. It's just easier to not depend on binary compatibility and always recompile.
I'm guessing this is a result of 'insane' processes where you have people upgrading dependencies in deployed applications without properly going through a test process.
(EDIT: oops i thought this was a c# post. but this change in java breaks source compatibility as well as binary compatibility)
- jacques_chester 9y agoMy understanding is that C#'s properties were designed pretty much exactly for this situation.