Status icon not visible (probably conflict with resharper) about azuredevopsstatusmonitor HOT 5 CLOSED

Hello Michael,

Thanks for reporting this issue. I use resharper as well and I have not had this issue. So I do not think it is caused by resharper. When solution is loaded, the animation area is in the middle beside Line number (you can build your solution to see the build icon - that is where the animation area). Can you please check whether icon is displayed in the middle?

Meanwhile, i will investigate from my side too. BTW, what OS version are you using? Is it Win 8 / Win 10?

from azuredevopsstatusmonitor.

OS: Win 8.1 pro

I realize now that I don't see the build animation icon, but a build progress bar instead:

need to investigate which plugin is doing this, and if is a plugin... 😄

from azuredevopsstatusmonitor.

It's the Enable rich client visual experience:

now I see the build:

and the vso status inspector as well (currently investigating the problem LoL):

I think this hint should be add in the package description, and in the github readme page, but better could be if it's possible to move that icon somewhere else (because a lot of developers has that option disabled to speedup visual studio), or manage the Enable rich client visual experience and use text instead of icon when rich client is disabled. What do you think?

from azuredevopsstatusmonitor.

Brilliant! That is a good find! Thanks for finding and sharing the root cause for it. I can replicate the issue now too.
Regarding, showing text when Enable rich client visual experience is enabled, I am sceptical using the text as it gets overwritten whenever you are building or editing the code. That is because VS actively uses it to update the information. Also, user might not like it if I constantly keep writing the status there as it might hide the useful information user wants to see. Right?

I agree that it needs to be in github readme and in the package help file.

from azuredevopsstatusmonitor.

I agree that it needs to be in github readme and in the package help file.

I think this could be enough for now.

from azuredevopsstatusmonitor.