David Kean

Having been around for Win8/UWP on the Visual Studio sides of things, these "restrictions" around referencing are more better described as Windows business rules (at the time) being enforced by...

> Yes, all types in those three assemblies now live in WinRT.Runtime.dll. How does that work on .NET Framework? Some of those assemblies contain projected types. I know the new...

@stevenbrix That image is of the SDK-based projects which is a different project-system, not .NET Framework projects.

.NET Framework physically contains those assemblies, they do not expose them in the targeting pack, ie the thing the developer compiles against which will be needed so that the compiler...

There's an entire section referring to this in the bug: > Desktop UWP Project References >Project references cannot be added in Visual Studio between Desktop and UWP (Universal Windows) projects....

Oh, C++ only?

Yes design-mode. I do not have a name of the component using the library, but there were a number crashes caused by this.

This will occur for any csproj that fails to load. This will be the whole "we're missing a single component from the .NET desktop development workload so assume this is...

I think we came to decision that we'll do this on per job/Repro basis. Here's the bug that's tracking it for Roslyn: https://github.com/dotnet/roslyn/issues/8553.

This is a CPS bug, we should get a Developer feedback item filed and moved to them.