Runtime missing for Universal 10 D3D build

When creating a D3D (DX11) build for the first time for an existing project I get:

The type or namespace name ‘Runtime’ does not exist in the namespace ‘System’ (are you missing an assembly reference?)

The project builds fine for XAML but wanted to test DX11. Is there an easy workaround? I’m using 5.2.3f1.

At what point exactly are you getting this error?

When I go to run / build the VS2015 project (Master x86)

And is it just an intellisense error, or does it prevent building the project when you do? Which part of the source code contains the errors according to VS?

ErrorCode CS0234 - which blocks the build

AssemblyAttributes.cs

using System;
using System.Reflection;
[assembly: global::System.Runtime.Versioning.TargetFrameworkAttribute(“.NETCore,Version=v5.0”, FrameworkDisplayName = “.NET for Windows Universal”)]

I believe all the other errors (112) are victims of the missing (Windows) System namespace.

This sounds weird. If you build an empty Unity project, does it work then?

The empty project works just fine. Strange that the same project builds to xaml fine.

Did you by any chance build on top of your XAML project? Unity should prevent that from happening with an error, but maybe something went wrong with the check.

I took a copy of the Unity project folder ([projectname] copy) and built that to a new folder [projectname]_W10DX. For some reason it can’t fine the Windows system namespace.

I guess it’s not a big deal as the xaml version works fine and I probably don’t have any good reason to move to DX builds (assuming the xaml build uses a swapchain for DX11 anyway).

Any chance we could get a bug report with a repro for that? It’s a weird issue, it would be awesome if you could at least zip up what Unity generated and PM it to me. I’d like to get to the bottom of what’s happening.

Is there any update on this bug? I get this error with both Xaml and DX11 project for UWP builds in Visual Studio?

I’m afraid we never received a bug report on this, and we aren’t sure what’s causing it. Could you submit a bug report?