Let’s be honest (its anonymous anyways) for .NET DEVELOPERS ONLY! Think about your normal build as you work (not a production build etc)
-
Upcoming Events
- DDD Exchange June 14, 2013 London
- Progressive.net vienna September 13, 2013
-
Archives
-
On twitter
- @coreyhaines @__Neha @twitter I hear it also works in a few common editors :-) 7 hours ago
- @TotherAlistair looked hard but didn't see certifications there... 8 hours ago
- @cory_foy your tax dollars hard at work 9 hours ago
- @zedshaw should be cool then. Make sure to go to Wawel early (non guided tours sell out) 12 hours ago
- @zedshaw where are you staying? I recommend either private apt or hotel wawelem (next to Wawel castle) 13 hours ago
5 Comments
What do you mean by build?
1) Build of the solution (ctrl-shift-b). Ours takes 2m45s. I never do this
2) Build the project you’re interested in + any dependencies. Ours takes 5 to 15 seconds
Neither of these run any unit tests.
For comparison, our CI build which runs unit and integration tests takes 15 minutes.
ctrl+shift+b would be the best measure but it varies heavily depending what you are building (incremental builds)
Full build takes slightly more than a minute. During normal development incremental one varies from 5s to ~45s (same as full, but without unit-test projects), so I picked <30s variant as somewhat in between.
When I start “all build” task, I can do things like that, read a blog and post a comment.. =D
When running tests that are integration test with the platform we develop on, no way to escape the penalty of waiting
2 Trackbacks
[...] did an informal survey a while ago and the results were frankly abysmal. I cannot understand how people work in such environments. I [...]
[...] did an informal survey a while ago and the results were frankly abysmal. I cannot understand how people work in such environments. I [...]