> Hi
> I use .net 2002 framework 1.0
> I have a huge .net solution consisting of many projects. Depending on
> the case, each time I change different project(s)
> It is extremely time consuming to build all projects every time I want
> to debug. Isn't there a switch somewhere to tell .net to build only
> what has been changed since last build?

<interuser@hotmail.com> wrote in message
news:a840cbfe.0403230702.18d7829a@posting.google.com...
> "Build Solution" builds everything.
> Isn't there a switch somewhere to tell .net to build only what has

"Hans Kesting" <news.2.hansdk@spamgourmet.com> wrote in message news:<ehua0NPEEHA.1544@TK2MSFTNGP09.phx.gbl>...
> <interuser@hotmail.com> wrote in message
> news:a840cbfe.0403230702.18d7829a@posting.google.com...
> > "Build Solution" builds everything.
> > Isn't there a switch somewhere to tell .net to build only what has
> changed?
>
> The default is to rebuild only what needs to be built. This includes
> projects that
> have changed, but also projects that depend on (=reference) those changed
> projects and probably also projects that depend on those (etc).
>
> The reason is that a change in a "lower" project could affect the higher
> ones,
> so that needs to be checked by recompiling.
>
> So, if you only change a top-level project, only that needs to be
> recompiled.
> If, on the other hand, you change a deep-down library project that is used
> everywhere, then everything will be recompiled.
>
> Hans Kesting

> If .net were clever enough, it would rebuild the dependent projects
> only when required: eg when the public method declarations change (and
> not the content)
> Let's hope this will happen sometime in the near future

Michael Bray <mbrayXXnoSPAMpleaseXX@SkPiAlMl.ctiusa.com> wrote in message news:<Xns94B69C3BF631Cmbrayxyzctiusaabccom@207.46.248.16>...
> > If .net were clever enough, it would rebuild the dependent projects
> > only when required: eg when the public method declarations change (and
> > not the content)
> > Let's hope this will happen sometime in the near future
>
> What if the public methods don't change, but the private functions that the
> public methods use do? You still need to recompile!
>
> -mdb

Michael Bray <mbrayXXnoSPAMpleaseXX@SkPiAlMl.ctiusa.com> wrote:
> > If .net were clever enough, it would rebuild the dependent projects
> > only when required: eg when the public method declarations change (and
> > not the content)
> > Let's hope this will happen sometime in the near future
>
> What if the public methods don't change, but the private functions that the
> public methods use do? You still need to recompile!