Hi,
Which is the point of running a solution without building their latest
changes? Properly speaking, there is no "Run" command, there are "Start" and
"Start without debugging". If you use the former, certainly you will want to
build before debugging since otherwise the exe and the sources could be out
of sync. The latter is rarely used and in fact it seems that its menu entry
was removed in VS 2005, but even if used, most people will want to run with
the latest thing compiled.
That said, you can always create a desktop shortcut to your exe in the bin
folder to run it.
Note: the option On Run, when projects are out of date applies only to C++
projects, as explained in the help of that dialog window.

Signature
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
> When using VS with C# projects, it seems like there is no way to
> disassociate building from running. More specifically, whenever I run
[quoted text clipped - 16 lines]
> Is there any way, in a regular C# Solution/Project, to turn this
> behavior off?
rrvade@gmail.com - 18 May 2006 11:51 GMT
You are right that running with the sources being out of sync does not
make much sense.
The problem is that VS tries to build even if there are no changes.
Although usually it's fast (msbuild figures out there are no changes
and skips all targets) it still takes time as it has to check every
single project.
In scenarios when you spend more time investigating the inner workings
of a program by debugging it, this becomes very inconvenient.
I know how to hit Ctrl-Shift-B myself, so I would like the option to
disassociate this action to "Start".
Carlos J. Quintero [VB MVP] - 18 May 2006 12:31 GMT
> The problem is that VS tries to build even if there are no changes.
> Although usually it's fast (msbuild figures out there are no changes
> and skips all targets) it still takes time as it has to check every single
> project.
You can check or provide feedback about this issue (if you think it is a
problem) or make a suggestion at the Microsoft Product Feedback Center:
http://lab.msdn.microsoft.com/ProductFeedback/

Signature
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
Sergey M - 18 May 2006 15:24 GMT
> The problem is that VS tries to build even if there are no changes.
> Although usually it's fast (msbuild figures out there are no changes
> and skips all targets) it still takes time as it has to check every
> single project.
One approach to consider is partitioning your solution into multiple
smaller solutions. You could set up several small solutions (with
fewer projects) and also have a master 'all' solution (with all
projects) for build process to use.

Signature
Sergey Mishkovskiy
http://www.usysware.com/dpack/ - DPack - free VS.NET add-ons
http://www.usysware.com/blog/
smartsw2006@hotmail.com - 30 May 2006 16:50 GMT
You can try this EnergyKey
http://www30.webSamba.com/SmartStudio
This may be help you.
Now I always use EnergyKey, it helps me so much in my work.