You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When MAUI .csproj value has multiple target platforms and includes either net6.0-tizen or net6.0-tizen8.0 the Emulator/Device selector stop working properly.
There are two possible outcomes:
If the Tizen is the first target in the list (eg. net6.0-tizen8.0;net6.0-android;net6.0-ios) the selector can be switched only to Tizen Emulator/Device. Doesn't matter what target device type I select (Android, IOS, Mac, Windows, Tizen) there will be only Tizen emulator or device assigned to the selector.
If the Tizen is at any position in the list other than the first one (eg. net6.0-android;net6.0-tizen8.0;net6.0-ios) the selector does NOT show Tizen Emulator/Device option at all. If I select Tizen as the target, the selector will get the Windows Machine with no other options.
.NET 6.0.428
Tizen workload: 8.0.154
VS 17.12.3
The text was updated successfully, but these errors were encountered:
Yeah, I know it was already reported to MS. But it doesn't look like they are going to handle this, because all built-in targets work just fine and the only one with that problem is Tizen. So apparently the issue sourcing from some Tizen tool chain. And MS consider Tizen and everyting around Tizen as Samsung's problems. Samsung is responsible for the Tizen.NET/MAUI support.
When MAUI .csproj value has multiple target platforms and includes either net6.0-tizen or net6.0-tizen8.0 the Emulator/Device selector stop working properly.
There are two possible outcomes:
.NET 6.0.428
Tizen workload: 8.0.154
VS 17.12.3
The text was updated successfully, but these errors were encountered: