1

When I create custom control that uses new Composition API from Anniversary Update, then Visual Studio Designer is broken:

enter image description here

However the application runs just fine.

Why is that? how to avoid it?

EDIT: Please, vote on UserVoice (Fix the UWP designer errors) so Microsoft will adress this issues finally.

Visual Studio 2017 is out for a while, two VS updates has been released and nobody adressing issues with UWP designer.

Liero
  • 25,216
  • 29
  • 151
  • 297
  • There are a lot of issues with the designer and the composition APIs. See https://github.com/Microsoft/WindowsUIDevLabs/issues/112 – Decade Moon Dec 13 '16 at 13:14

2 Answers2

0

I had the same issue. I was adding an instance on my view model within the XAML file itself.

enter image description here

I removed that and the designer was back!

Community
  • 1
  • 1
bit
  • 4,407
  • 1
  • 28
  • 50
0

I partially solved the problem by using animation helpers and controls like DropShadowPanel from https://github.com/Microsoft/UWPCommunityToolkit and upgrading to Visual Studio 2017 and installing all updated and installing latest windows update (creators)

UWP designer sucks anyway, but at least some views works, when I do not use composition api directly.

If you are experiencing simmilar issues, vote on UserVoice: Fix the UWP designer errors

Liero
  • 25,216
  • 29
  • 151
  • 297