XAML files are not supported

[srivatsn]

From @tannergooding on February 3, 2017 22:56

Attached is a simple repro solution. WpfCps.zip

Issue 1: XAML files are treated as None, when they should be treated as Page with Generator=MSBuild:Compile and SubType=Designer metadata. Issue 2: Page items are not visible in the Solution Explorer Issue 3: xaml.cs files are not properly nested under the xaml file Issue 4: Compilation fails with: 1>C:\windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.WinFx.targets(419,45): error MSB4057: The target "CoreCompile" does not exist in the project.

Copied from original issue: dotnet/sdk#810

[gulbanana]

There is imperfect XAML support already in the 3.0 nightly builds - pre-alpha stuff, but it’s definutely being implemented. I would expect full support (designer etc) to require vs2019. In the meantime, the workarounds people have described above are still functioning; I have a bunch of WPF libraries and applications using SDK projects.

[davkean]

Project system support, as per our roadmap https://github.com/dotnet/project-system/blob/master/docs/repo/roadmap.md, is in the 16.x timeframe.

[davidwengier]

Closing this as Xaml is now well supported in 16.1 and we have individual issues for the few gaps that remain. If there is a comment in this thread that represents something that is still an issue in Visual Studio 2019 please log a new issue.

The issues that are still pending for Xaml support can be tracked here: https://github.com/dotnet/project-system/issues?q=is%3Aopen+is%3Aissue+label%3AFeature-XAML

Other teams will also have work pending (eg. the designer) but the workarounds called out in this thread should generally be no longer needed.

[DzonnyDZ]

I posted possible (nasty) workaround for the issues with 2-pass build here: https://github.com/dotnet/project-system/issues/5252