How Remove WinRT APIs from .NET 6 Project.

RogerSchlueter-7899 1,236

I am getting this error:

Microsoft.Toolkit.Win32.UI.XamlHost.Managed.dll cannot be referenced because it uses built-in support for WinRT, which is no longer supported in .NET 5 and higher. An updated version of the component supporting .NET 5 is needed. For more information, see https://aka.ms/netsdk1149

I have been to the referenced web site and made the recommended changes to my project file. The relevant line now reads:

<TargetFramework>net6.0-windows10.0.22621.0</TargetFramework>

I do not know additional steps I need to take to remove this error? I am aware that I may need to provide more information to allow answers but I'm not sure what else to provide. I'll be happy to add more in response to comments.

Roy Li - MSFT 32,051 Reputation points Microsoft Vendor

2022-09-15T01:21:02.593+00:00

What kind of application are you developing now? Is it a WPF application or a UWP application? And could you please share the document that you are following?
RogerSchlueter-7899 1,236 Reputation points

2022-09-15T04:24:37.973+00:00

Oops, I left off that info. It's a wpf, desktop, .NET6 application.

The error message takes you here. I completed the first step under "Recommended Action" as shown in the XAML postedm above.
Hui Liu-MSFT 40,266 Reputation points Microsoft Vendor

2022-09-15T06:21:57.337+00:00

Hi,@RogerSchlueter-7899 . As the documentation says, is your project consuming a third-party runtime component that's defined in a .winmd file? If so, you could add the Microsoft.Windows.CsWinRT NuGet package and refer to the C#/WinRT documentation. And is your project running properly now? If not, is there an error message?
RogerSchlueter-7899 1,236 Reputation points

2022-09-15T20:31:37.623+00:00

I don't think and third-party component is using WinRT. That said, I don't know that. My project itself does not have a .winmd file.

This is a VB project. When I added the NuGet package it went belly up in numerous places. Does my using VB negate the usage of that package? I wouldn't think so.

In short, I'm back to square one.
RogerSchlueter-7899 1,236 Reputation points

2022-09-16T01:12:55.99+00:00

I went back to an earlier version which is working so I want to temporarily drop this issue. As I restore portions of the project that were lost, I'll keep a very close eye open for when this error pops up again. At that time I should have much better definition of what the problem really is.
Hui Liu-MSFT 40,266 Reputation points Microsoft Vendor

2022-09-16T03:17:57.9+00:00

OK, welcome back if you have any further questions.