Replies: 1 comment 3 replies
-
@pedasmith IBuffer is indeed still supported. What is the TFM for your .NET 6 command line program? Are you targeting a Windows OS version-specific TFM to get access to the Windows WinRT API surface and thereby IBuffer as discussed in step 2 of here? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've already got a big chunk of code written for UWP; it's intended to connect to Bluetooth devices and, as part of that, provides interfaces that use the IBuffer interface that UWP uses everywhere. I'm trying to use this code, unchanged, in a .NET Core 6 command line app.
When I try to make a .NET Core (6) command-line program that re-uses these UWP classes (via a "shared code" project, so I'm literally just sucking these .CS files into my project), I get tons of errors that "Error CS0012 The type 'IBuffer' is defined in an assembly that is not referenced. You must add a reference to assembly 'Windows, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null, ContentType=WindowsRuntime'."
It's frankly driving me nuts. There's ton's of blog posts and stack overflow comments, but each and every one is not applicable: they suggest I do things that are obsolete since .NET 5, or only for the framework, or are incompatible.
Help!
Beta Was this translation helpful? Give feedback.
All reactions