compile fast, build _sloooow_

when i compile one of the projects in my solution, the 'compile' time is very short: the 'compile complete' message appears almost emmediately. (this is with the public beta of vs2005)

however, afterwards, the ide will begin to do things on the hard drive for up to 2 minutes (each time !). after that, the 'build succeeded' message appears.

what is it doing in this time what can i do against that  this makes it almost impossible to work with the ide.

WM_QUERY
thomas woelfer
http://www.die.de/blog
 


Answer this question

compile fast, build _sloooow_

  • mrodriguezc

    Oops, thats only for Visual Studio 2005. If your problem exists in VS2003, then I have no idea.


  • rhyd

    what do you mean by 'custom control' a class derived from system.windows.forms.control or system.windows.forms.form

    in that case, i guess i have about 30-40 'control' (or usercontrol) derived classes and maybe some hundred or so forms.

    WM_THX
    thomas woelfer
    http://www.die.de/blog


  • misbrisco

    Wow,

    thank you!

    that changed things a lot. the ide just went from 'barely useable' to 'fast'.

    WM_THXALOT
    thomas woelfer
    http://www.die.de/blog


  • Ben0s

    Oh, great :)


  • Shanta Appukuttan

    Do you have a lot of custom controls


  • jstar

    Try this:

    Tools->Options->Windows Forms Designer->General->AutoToolboxPopulate=false;

    I ran into the same problem. I was wondering why the heck it took so long for it to finish the build. One time, when I compiled  with one of my controls open and the toolbox visible, I saw that all of the controls were re-added to the toolbox after the compile, which is where the 30 seconds of waiting was coming from. I poked around the IDE to find an option to turn off this toolbox update, and sure enough disabling it makes the compile super fast just like a brand new project.

    Obviously, when you want to drag and drop your new custom controls onto your forms you will have to re-enable that flag temporarily so the toolbox is updated. But it is worth the effort to leave it disabled when doing normal coding.

    I hope that fixes your problem.


  • John rambo

    well i wasn't looking for a tool to track down what the ide is doing: whatever it is, i want the ide stop doing it...

    WM_CHEERS
    thomas woelfer
    http://www.die.de/blog

  • Dazza1412

    I had a similar problem.  I had a Database project in my solution.  The IDE was copying the (very large) database file to the Debug directory.  I'd suggest using the tool mentioned above to see what's happening.  Only then should you decide whether or not it's Visual Studio's fault.  ;)

  • JimSeidel

    http://www.sysinternals.com/Utilities/Filemon.html

    Sysinternals has a tool that displays file system activity.


  • bY73-_-j0b

    well - so i looked.

    the devenv is doing about one gazillion things. its certainly not copying any unwanted files to the runtime directory, because that directory only contains the dlls needed by the application.

    its impossible to find out what exact request from the devenv is causing that delays: its running so many requests - how am i supposed to find out which one is the 'slow' one maybe there event isn't a 'slow' one - only an etremly large amount of 'normal' ones

    well anyhow, still can't get productive with this.

    WM_SLOW
    thomas woelfer
    http://www.die.de/blog

  • compile fast, build _sloooow_