We changed the code to wrap the lines because long error messages weren't readable. We weren't able to overhaul the build details view in 2008, but it's been completely redone for TFS 2010 (see http://blogs.msdn.com/buckh/archive/2008/10/19/tfs-build-2010-build-summary-screen-shots.aspx if you are curious).
One thing that may help is to maximize the VS window to minimize the wrapping. William also mentioned the fact that a fix for an issue that exacerbates the problem is currently winding its way through the machine. When that fix is finalized, it should be available with the on the code gallery site with the rest of the tfs patches. Buck From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John McFadyen (Intl Vendor) Sent: Tuesday, November 04, 2008 6:39 PM To: [email protected] Subject: RE: [OzTFS] Build Log window Hi William, Basically since the install of VS2008 SP1 all build steps now line wrap. It seems the window width is now limited which of course causes the line wrap. Due to the line wrap we obviously hit the 65k pixel mark mentioned earlier by Grant. I have attached a screen dump of some of the items affected. This is definitely a result of SP1 as a colleague had the same issue for a while and he suspected SP1 was the culprit. I installed SP1 on my machine this week and now I have the same issues as him. This is not the end of the world but if it could be fixed it would be good. I will try the verbose options supplied by Grant and see how I go. Regards, John From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of William Bartholomew Sent: Wednesday, 5 November 2008 8:43 AM To: [email protected] Subject: Re: [OzTFS] Build Log window Hi John, What particular build steps are the issue? William On Tue, Nov 4, 2008 at 12:52 PM, John McFadyen (Intl Vendor) <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: Hi all, We have some very large projects which for some time reaching the window buffer size limit for the build log window causing and following messages to be dropped from the build output window. To alleviate this issue we modified our build step output to write similar entries on a single line, successive entries of the same type of process would overwrite the same line reducing the required window space resolving our issues. I have now installed Visual Studio SP1 which has introduced another issue similar to the above. When we have build steps which have large message output the messages are word wrapped. This in turn means that build step output again takes up more window space. The result of which is of course we again reached our window output limit. Is there a way to stop word wrapping of build step messages. Or even increase the Build Log windows buffer space ? Regards, John McFadyen | Release Management - ICMS Project | | Independent Contractor to Microsoft Australia | m +61 424 789 747 | mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com<http://mailenable.com/>, supported by www.readify.net<http://www.readify.net/> OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net
