3 ms·
And TFS can't handle path lengths longer than 260 characters. I don't want to hear the BS about MAX_PATH. These are really annoying customer-facing flaws that
by shaggyfrog 13y ago
And TFS can't handle path lengths longer than 260 characters.
I don't want to hear the BS about MAX_PATH. These are really annoying customer-facing flaws that scream "amateur hour".
- InclinedPlane 13y agoYup. All due to a choice someone made when deciding how to wrap the win32 file system APIs for dot-net. Also, if you think that's bad, how about this. The TFS build system schedules builds on agent machines using a time format of UTC time of day. Seems fine except for that it is utterly broken in the context of daylight saving time. If you schedule builds that you want to run at a particular local time of day, which almost everyone does as it's an exceedingly common use case, then the actual time of day that build runs will be determined by whether or not the build definition was last saved during the current DST period. For example, if you have a bunch of build definitions and daylight savings time had just ended then builds could run either on time or an hour early.