Vikas Gupta

I have a question why the below mentioned code snippet is a forever loop in C# 2.0... I haven't tested it in > 2.0 frameworks but I bet the behavior won't be different..

for (byte index = byte.MinValue; index <= byte.MaxValue;  index++)
{
    // do something forever untill the stack is exahausted...
}

I know the reason but I would like to know the what was exact design decision related to it the way post increment ++ operator is implemented for the BCL type BYTE...

Email: tricky.vikas@gmail.com / gupvikas@hotmail.com     

Hi Jim,

A product enhancement request related to Project Alerts area w.r.t. Team Builds. As of now, TFS provides 2 team project level related to team builds i.e.,

1. When a build completes
2. When a build quality changes

But in practical world, the audience/stakeholders for these alerts is always different for each build type lets say a scenario for Daily Build vs Bi-weekly build or Development Build vs Release Build. Same holds true for the build quality changes of these builds. A QA / UAT / PRODUCTION resource is not interested in all the builds and its quality changes except the Release Build.

Request : So, It would be nice to have Build Alerts a part of build type definition itself. The project alerts at the team project level will still be beneficial at the project team level / project managers and above ....