| T O P I C R E V I E W |
| netics |
Posted - Jun 15 2008 : 10:41:01 PM
our source code is so big. over millions. maybe many ppl, too.
build time is long and long.... so I often surf internet while building.
then i have to check VS repeatly for build completion.
it's also happened that i devoted surf, forgetting completion.
it will be nice that when build completed, message pops like msn messenger.
and notyfing message should be appeared immediately when build error happens.
how about this idea? |
| 9 L A T E S T R E P L I E S (Newest First) |
| netics |
Posted - Jul 16 2008 : 8:09:12 PM
oh, feline. :-)
I hope that VA makes that others don't have to edit 90 projects by hand. |
| feline |
Posted - Jul 16 2008 : 1:57:44 PM
How many projects do you have, and how often do you add new projects?
I once worked on a solution with around 90 projects in it, and that was just about the biggest number of projects I have ever seen, or heard anyone report using. |
| netics |
Posted - Jun 17 2008 : 01:35:28 AM
Uniware//
Thanks. With your recomendation, I tried Event Toaster.
It works well. BUT... not enough. It has just a simple feature.
1. It notifies when build done. It will be better that notifying immediately when build error happens.
2. It makes tray icon for every instance of VS. I normally works with 3 instance of VS. 3 tray icon is really cumbersome.
3. It only handles 2 event. Build Done and Parsing Done. But it regards every task with output window as Build Done.
When i just compiled one file, it pops. When i clean the project, it pops. When i execute with debugger, it pops. so on....
and it don't have any information like success or fail.
feline//
There is one more reason that editing project file is not good.
I have to edit every project when I make it.
|
| Uniwares |
Posted - Jun 16 2008 : 9:42:37 PM
http://blogs.msdn.com/aaronmar/archive/2006/07/19/671687.aspx
Solves your problem perfectly. |
| netics |
Posted - Jun 16 2008 : 8:43:59 PM
quote:
You could write the macro, but make sure it does nothing by default. Add this "does nothing" macro to source control, and then edit the macro on your local machine so that it is active.
no. no.
what i want is solution not to touch project file, working locally.
others may not like just null macro. |
| jameso |
Posted - Jun 16 2008 : 10:01:20 AM
Isn't there a powertool which does this? (Toaster or something) |
| feline |
Posted - Jun 16 2008 : 08:59:36 AM
You could write the macro, but make sure it does nothing by default. Add this "does nothing" macro to source control, and then edit the macro on your local machine so that it is active. |
| netics |
Posted - Jun 16 2008 : 06:47:04 AM
i know. but it change project file in source control system.
i don't work alone. others may don't want it.
|
| .oisyn |
Posted - Jun 16 2008 : 06:33:02 AM
You could write a simple macro and attach it to the OnBuildDone event. |
