Thank you all for the details!

Whilst this is going through, could you please try the following?
- Connect the dock and monitors as usual,
- Change the Windows Display Settings so the Primary is NOT a DisplayLink monitor (for instance the embedded panel of a laptop will do).
- Launch VS XAML.

Does VS crash in this condition?

Hi Alban,
Yes, the XAML Designer crashed with this seetings too.

ckruhs

There was an update on VS Connect.
It now looks likes it's now being handled as an application issue as we first hinted.

"Posted by Mark [MSFT] on 23/09/2016 at 22:41
Thank you for reporting your issue with Visual Studio. This issue has now been fixed, and will be released with (the next update) to Visual Studio."

Latest update I got is that the message on VS Connect is incorrect.
This is not a VS issue but an OS issue.

In all cases MS tried, making the primary screen not an indirect display solves the issue.
Therefore, even if they are looking to address it, this is not an emergency for them and they want to make sure the change they make doesn't create collateral damage. This is under compatibility test and there is currently no delivery date.

Thanks for the information.

In my case I continue my XAML development without DL. Pain.

But there are bigger problems with DL+8.0M2+1607. Huge lags, every time connect-disconnec-connect-disconnect DL device, my computer gets more laggy, mouse stopps, processor high. But, ONLY when it connected. looks like something fell out of sync. I have to restart several times a week for the normal performance.

Is there any information?

For what it is worth, I have the exact same crash with my XPS15 and D3100 docking station. 2 external displays, 1 to the DisplayLink dock and 1 to the XPS15 HDMI output. (Lid closed on the laptop)
Making my non-displaylink display (HDMI, forced to the Nvidia graphics adapter in my case) the "Main display" solved it for me at least.

/M

Hello CMJ,

Yes. Because there is a relatively easy workaround, and because a lot of the surrounding code was changed causing compatibility risks, we have stopped pushing for the fix to be backported to RS1 builds.

I hope everyone agrees we don't want to take the risk of making it worse and potentially impacting wider features than "main display", accepting it as a temporary limitation until RS2 hits release stage.

Kind regards,
Alban

Stupid design. Beta software. Untested code and upgrade. Angry customers.

"We stopped..... until RS2". Till 2017Q2???

Nice work. :-(

Hamurabi,

The bug that Microsoft has identified can be worked around by assigning the primary graphics card display as main display.
Would you rather risk it for the convenience of have the systray on another display? I would not and I am being transparent about it.
If you have another issue with Visual Studio XAML Designer, you might wish to direct your anger to the people who can solve it by creating a support ticket to the Visual Studio team.

Regards,
Alban