![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Build Selection - Rebuild Selection Build Solution - Rebuild Solution Batch Build There must be a difference between build and rebuild. For some reason, it doesn't seem to matter which one I choose, but I suspect there is some underlying principle of which I am unaware. Can someone please elucidate? -- Regards, Jamie |
#3
| |||
| |||
|
|
"thejamie" <thejamie (AT) discussions (DOT) microsoft.com> wrote in message news:2A3AC338-A96F-45F1-8980-E538DE7AD6B8 (AT) microsoft (DOT) com... Build Selection - Rebuild Selection Build Solution - Rebuild Solution Batch Build There must be a difference between build and rebuild. For some reason, it doesn't seem to matter which one I choose, but I suspect there is some underlying principle of which I am unaware. Can someone please elucidate? -- Regards, Jamie It won't matter much with a small solution. Build selectively rebuilds only those parts of a solution (or named project) that have changed since the last build. Rebuild unconditionally rebuilds everything in your solution (or project, depending on whether you choose Rebuild Solution or Rebuild "project name". -- Peter [MVP Visual Developer] Jack of all trades, master of none. |
#4
| |||
| |||
|
|
Would there be any benefit for the person installing the product if I were to use Build instead of Rebuild, or is it transparent on their part. I infer, perhaps erroneously, that it may speed up their re-installation process if I choose build rather than re-build. You have piqued my curiousity here. Is Build analogous to a Patch, (as in MsiMsp.Exe w/ patchwiz.dll...) or are these totally different objects? These commands are internal to the development process within Visual Studio |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |