Have you applied Team Foundation Server Service Pack 1 to your build machines? It is meant to remove the extra build steps you're seeing such as GetTargetPath, GetNativeManifest, and GetCopyToOutputDirectoryItems. We have had some issues where it doesn't always fix this issue but in most cases it seems to. We've been working with the development team to fix the scenarios where it doesn't.
William On Wed, Nov 5, 2008 at 9:39 AM, John McFadyen (Intl Vendor) < [EMAIL PROTECTED]> wrote: > 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]> 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 <livecall:424789747>| > 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, 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 > 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
