6

I have a custom MSBuild task that takes some time to complete. It outputs progress using either Log.LogMessage() or BuildEngine.LogMessageEvent() (tried both).

My problem is that all output doesn't appear in VS2012 Output window until the task is completed, making progress updates useless. I would like to have output appearing while the task is running, right away.

I found various threads explaining to call frequently Application.DoEvents(), but that doesn't seem to solve the problem (maybe it only applied for VS2010 and before?).

2
  • 3
    This appears to be a known bug in VS2012 (and I can confirm it also occurs in VS2013) and in usual Microsoft fashsion its status is "can't be bothered to fix". connect.microsoft.com/VisualStudio/feedback/details/790444/… Needless to say, it is incredibly annoying. Did you ever find a workaround? Commented Aug 12, 2014 at 8:16
  • In VS2012 we had to VSPackage extension to directly output in pane log. Seems like VS2015 fixes the issue though. Commented Nov 25, 2015 at 8:46

2 Answers 2

1

Known bug in VS2012.

We ended up making a VSPackage extension for VS2012/2013 (to directly output in pane log).

It is fixed in VS2015.

Sign up to request clarification or add additional context in comments.

1 Comment

I'm using VS2017 and having the same issue. Is there anything that has to be set up for this to work?
0

It is a bug in VS 2012. In the comments in this bug report a user whose alias is Will, speaking on behalf of Microsoft, wrote on July the 2nd of 2013 that Though we will not have a chance to address this issue in Visual Studio 2012, we will consider this feedback when planning for future versions of Visual Studio.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.