VS2012 Workflow Designer has bugs when used under high DPI settings - by Eran Stiller

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 773496 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/5/2012 12:11:29 AM
Access Restriction Public


When Windows is set to use high DPI scaling (e.g. 125%), VS2012 Workflow Designer has many quirks when trying to use the Base Activity Library activity designers.
For example, editing the field of "Target Object" on the "Invoke Method" activity designer or the "Condition" field on the designer of "If", "While", "DoWhile" etc. causes these fields to blink, vanish or other weird results making the WF designer impossible to use.
Sign in to post a comment.
Posted by Deon [MSFT] on 4/29/2014 at 12:31 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Microsoft on 6/27/2013 at 2:45 PM
Thank you for reporting this issue. We have fixed it for the next version of Visual Studio.
Posted by Eran Stiller on 1/13/2013 at 10:29 PM
Any news on the status of this issue? It has been more than a month with no comments...

Posted by Eran Stiller on 12/7/2012 at 4:39 AM
Just wanted to add that I've also reproduced this behavior on a Windows 8 machine with VS2012.
Also note that the VS2010 WF designer works flawlessly under an identical scenario.
Posted by Microsoft on 12/5/2012 at 1:54 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 12/5/2012 at 12:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)