VS Code - AudioPlayerOptions does not contain definition for CategoryOptions

[whann0205]

Cannot build solution on the mac with Visual Studio Code
because of that error, in Visual Studio 2022 running from a windows machine
it compiles just fine and the simulator runs without any problem.
If i open the definition from VS Code i can see that its somehow does
not have the correct context.
I dont know how i can change the framework context in vscode.
They only thing which i can do is click on the brackets select as target
my iphone.
I can overcome that thing for the moment since i am able to deploy
via visual studio 2022 on windows (remote device).

[SchittkowskiMS]

Same error happens when calling dotnet publish on a mac when trying to create a version to upload to appstore

[whann0205]

I have found the problem source
see microsoft/vscode-dotnettools#1522
It seems that they opened a bug on that, but i did not
get any message from anybody. Also i am not sure if its a bug or
simply something i (we?) dont know.

[whann0205]

@jfversluis Can you help us out, since there is no reaction from the vscode Team?

[bijington]

The property only exists on iOS and MacCatalyst, your screenshots show that you aren't guarding the code with a #if therefore it's trying to compile for all platforms. Does it work if you place the #if from the commenter out section below?

[SchittkowskiMS]

i had it guarded by #if, had no issues to compile in visualstudio on windows and debugging to ios device. the error seems to be happening only when compiling on mac

[bijington]

Do you have the same .NET SDK and MAUI workloads installed on both machines? To check this you run the following in command prompt/terminal:

Dotnet SDK
dotnet--info

Workloads
dotnet workload list

[whann0205]

Since it is a compiler error from vscode i doubt that i has something to do
with the dotnet version or installed workloads does it?
They are indeed very different though, i can post the output of both commands
on the machines if it helps.

[bijington]

There is no compiler in VS Code it will be using whichever compiler is installed as part of whichever .NET SDKs are installed.

The workloads might have something to do with it. It will be much easier to prove once I know what workloads you have installed

[whann0205]

Alright, here you go!

dotnetmac.txt
dotnetwin.txt
dotnetwlmac.txt
dotnetwlwin.txt

[whann0205]

OK, i have an update for you all.
I deleted dotnet completely from my mac (everything),
installed the latest .net8 sdk, restored workloads.
Now all is working.
Thank you for pointing in the right direction,
didnt know that the sdk has that impact on the source.
Strange though.

[bijington]

Thanks for the update. We have recently discovered that workloads can impact which TFM is being targeted when the NuGet package is built. At times this can be painful especially when you have certain preview builds installed. Glad it's solved it for you