By Peter Jones - 9/21/2009
Hi,
It used to be that when I set a project to be the 'start-up project' in VS and clicked run then that project and all its depedancies where rebuilt but now my entire solution is rebuilt.
I've no idea what I've modified to cause this behaviour change but I would sure love to set it back to how it was. Any ideas?
Cheers, Peter
|
By Trent L. Taylor - 9/25/2009
If you are on VS2008 the only reason it would do this is if a downstream reference assembly is though to have changed. That is generally what sparks a rebuild.
|
By Peter Jones - 9/27/2009
Hi Trent,
Thanks for the info. Yes, we are using VS2008 - do you have any idea how I can 'set' the state of all assemblies to 'unmodified'? I've done a clean / rebuild of my solution many times and this doesn't change things.
Cheers, Peter
|
By Trent L. Taylor - 9/29/2009
Are you using VB.NET or CSharp? This can make a difference as well. If you are using VB.NET, then one way may be to use file references versus project references. This will also improve performance within the designer as well. If you already have it setup this way then you may try swapping to project references to see if you have any luck.
One thing that I will do at times, regardless of language, is to "smoke" (Texan for delete) my local working folders and re-download everything from source control and rebuild. This ensures that there are no rogue assemblies within my development environment causing me grief.
|
By Peter Jones - 9/29/2009
Hi Trent,
We use VB and I will certainly try you suggestions when I return to the office next week. Not sure what you mean by 'file references' but I guess I can suss that one out.
Cheers, Peter
|