Visual studio XAML designer crashes when DL docking station is connected

AlbanRampon · 09-12-2016, 03:13 PM

Hello,
I will ask tomorrow but I would expect this to be linked to Visual Studio not dealing with this new OS feature correctly rather than the OS as otherwise all other applications would trip on the carpet the same way.

On VS Connect, MS asked for logs. I'm not sure anyone who has a reproduction has chimed in, yet, but I think it would be helpful to get this progressed.
https://connect.microsoft.com/Visual...etails/3101540
My ticket to the Microsoft Sysdev portal has not been looked at yet.

Kind regards,
Alban

AlbanRampon · 09-14-2016, 05:32 PM

Hello,
Our bug report has been handed over to the Visual Studio team. I've been told they should now have an internal reproduction of the crash to debug it.
MS graphics team did not see how DisplayLink driver could be the root cause and they explained to the VS team the change made in the new Windows 10. I understand that doesn't really help the immediate resolution of the problem, but we have assistance and interest from within MS, and that is always helpful to get a solution. DisplayLink also uses VS.
Kind regards,
Alban

ckruhs · 09-15-2016, 06:46 AM

Hi Alban,
Thanks for the update :-)

Best regards,
ckruhs

AlbanRampon · 09-15-2016, 03:17 PM

Hi everyone,

I have some news. A solution has been found and we are discussing how this can be rolled out.
Unfortunately, this is not a VS fix but an OS fix. If you could tell me how many people are affected in your organisations, this would be most helpful for me to explain why this should be serviced in build 14393 as opposed to wait until the next OS version.
I already got that DisplayLink is losing business over this as some of you have been buying the non-universal TB2 solution instead of the universal USB one...

Kind regards,
Alban

ckruhs · 09-16-2016, 06:05 AM

Hi Alban,

we are a Microsoft Gold Certified ISV Partner with 20+ developers.

Best regards
Carsten

Hamurabi · 09-16-2016, 01:55 PM

Hi!
We have only 6 developer. But it's currently stopped us to use DL things. We have to do our development with only one direct connected HDMI monitor instead of two.

AlbanRampon · 09-19-2016, 06:55 PM

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?

ckruhs · 09-20-2016, 05:55 AM

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

ckruhs

AlbanRampon · 09-26-2016, 02:06 PM

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."

09-12-2016, 03:13 PM	#1
AlbanRampon Senior Member Join Date: Sep 2015 Posts: 1,685	Hello, I will ask tomorrow but I would expect this to be linked to Visual Studio not dealing with this new OS feature correctly rather than the OS as otherwise all other applications would trip on the carpet the same way. On VS Connect, MS asked for logs. I'm not sure anyone who has a reproduction has chimed in, yet, but I think it would be helpful to get this progressed. https://connect.microsoft.com/Visual...etails/3101540 My ticket to the Microsoft Sysdev portal has not been looked at yet. Kind regards, Alban __________________ Alban Rampon Senior product manager, universal docking stations and accessories Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

09-14-2016, 05:32 PM	#2
AlbanRampon Senior Member Join Date: Sep 2015 Posts: 1,685	Hello, Our bug report has been handed over to the Visual Studio team. I've been told they should now have an internal reproduction of the crash to debug it. MS graphics team did not see how DisplayLink driver could be the root cause and they explained to the VS team the change made in the new Windows 10. I understand that doesn't really help the immediate resolution of the problem, but we have assistance and interest from within MS, and that is always helpful to get a solution. DisplayLink also uses VS. Kind regards, Alban __________________ Alban Rampon Senior product manager, universal docking stations and accessories Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

09-15-2016, 03:17 PM	#4
AlbanRampon Senior Member Join Date: Sep 2015 Posts: 1,685	Hi everyone, I have some news. A solution has been found and we are discussing how this can be rolled out. Unfortunately, this is not a VS fix but an OS fix. If you could tell me how many people are affected in your organisations, this would be most helpful for me to explain why this should be serviced in build 14393 as opposed to wait until the next OS version. I already got that DisplayLink is losing business over this as some of you have been buying the non-universal TB2 solution instead of the universal USB one... Kind regards, Alban __________________ Alban Rampon Senior product manager, universal docking stations and accessories Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

09-19-2016, 06:55 PM	#7
AlbanRampon Senior Member Join Date: Sep 2015 Posts: 1,685	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? __________________ Alban Rampon Senior product manager, universal docking stations and accessories Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

09-26-2016, 02:06 PM	#9
AlbanRampon Senior Member Join Date: Sep 2015 Posts: 1,685	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." __________________ Alban Rampon Senior product manager, universal docking stations and accessories Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

09-15-2016, 06:46 AM	#3
ckruhs Junior Member Join Date: Sep 2016 Posts: 5	Hi Alban, Thanks for the update :-) Best regards, ckruhs

09-16-2016, 06:05 AM	#5
ckruhs Junior Member Join Date: Sep 2016 Posts: 5	Hi Alban, we are a Microsoft Gold Certified ISV Partner with 20+ developers. Best regards Carsten

09-16-2016, 01:55 PM	#6
Hamurabi Junior Member Join Date: Sep 2016 Posts: 12	Hi! We have only 6 developer. But it's currently stopped us to use DL things. We have to do our development with only one direct connected HDMI monitor instead of two.

09-20-2016, 05:55 AM	#8
ckruhs Junior Member Join Date: Sep 2016 Posts: 5	Hi Alban, Yes, the XAML Designer crashed with this seetings too. ckruhs

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode