C# code builds all the time whether it is current or not
-
Using C# and the VS2005 IDE SP1 Whenever I run my C# projects through the IDE it always goes through the build process whether the code is current or not. Is this normal? Can it be turned off as it is a waste of time? Any help appreciated. Thanks in advance.
Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
Using C# and the VS2005 IDE SP1 Whenever I run my C# projects through the IDE it always goes through the build process whether the code is current or not. Is this normal? Can it be turned off as it is a waste of time? Any help appreciated. Thanks in advance.
Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain)It may appear to be going through the build process all the time, but in fact it's actually just evaluating whether it needs to build anything. Unfortunately this seems to take just as long as just building the code would have done. You can tell the difference: if it actually builds anything, it will output the compiler command line. If not, it won't.
Stability. What an interesting concept. -- Chris Maunder
-
It may appear to be going through the build process all the time, but in fact it's actually just evaluating whether it needs to build anything. Unfortunately this seems to take just as long as just building the code would have done. You can tell the difference: if it actually builds anything, it will output the compiler command line. If not, it won't.
Stability. What an interesting concept. -- Chris Maunder
It seem that is does not just evaluate. It goes through the post and pre build steps too as my tlb's are updated. I'll investigate a little further, thanks for your reply.
Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
It seem that is does not just evaluate. It goes through the post and pre build steps too as my tlb's are updated. I'll investigate a little further, thanks for your reply.
Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain)The pre build step will always run. If the pre build step changes some source files/other input to the compiler, the project will be compiled again. For the post build step, there's an option if it should always run or only when the compiler updated the output file. Ensure your pre build step doesn't write to any files (does not modify the "last write time" of the files) if its input didn't change.
-
The pre build step will always run. If the pre build step changes some source files/other input to the compiler, the project will be compiled again. For the post build step, there's an option if it should always run or only when the compiler updated the output file. Ensure your pre build step doesn't write to any files (does not modify the "last write time" of the files) if its input didn't change.
Thanks for this. I have re-evaluated my pre-build activities and I have been able to move ones that would alter any files to run in post-build when the output has been changed. Many thanks again.
Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain)