I am having an issue with Visual Studio 2008 SP1. Basically, I have a .NET 3.5 solution with a client, shared and server component. While coding, all components run on the same box, but in production the server component is a standalone (remoting) service running on a separate server.
I would expect that a change to the client component would require only a rebuild of that component as there is no client/server dependency. This is in fact how it works on my work PC. However, on my personal PC and another co-worker's PC, any modification - even a simple label change on the client, requires the server component service to be stopped so that the solution can be rebuilt in its entirety. Does anyone know if there is a particular setting that controls this??
OK folks. The problem was more simple than I at first thought. On the PCs that this did not work as desired I had to turn on the Visual Studio setting (Options->Projects and Solutions->Build and Run) named "Only build startup projects and dependencies on run". This appears to have solved my problem.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With