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
Visual Studio 17.10.0 Preview 2's MAUI Project Property Editor is pretty hopeless. Currently, it does not recognize almost any conditions written in the project property file, and even is a bit bugged with writing some potentially non-functioning conditions of the style Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Debug|net9.0-ios|AnyCPU' where $(Platform) in fact may not work (perhaps is null?).
It would be much better if for each item in the property editor, instead of just having a simple tick box, the editor would scan the project property file and list each of the conditions it finds for that item, including no condition (applies always). Then you could click on the condition, and perhaps change the value in the project property file under that condition (almost like directly, a bit like search text functionality in VS). And if the entry would not exist, the editor would show what it would be adding to the project file, a bit like in Git Changes. It could even suggest typical conditions that people use such as:
Condition="'$(TargetFramework)'=='net9.0-ios' or '$(TargetFramework)'=='net9.0-maccatalyst'"
Finally, the editor could run some summaries what the conditions mean in terms of various platforms, and also present default values if some relevant platform is not covered by the conditions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Visual Studio 17.10.0 Preview 2's MAUI Project Property Editor is pretty hopeless. Currently, it does not recognize almost any conditions written in the project property file, and even is a bit bugged with writing some potentially non-functioning conditions of the style
Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Debug|net9.0-ios|AnyCPU'
where$(Platform)
in fact may not work (perhaps is null?).It would be much better if for each item in the property editor, instead of just having a simple tick box, the editor would scan the project property file and list each of the conditions it finds for that item, including no condition (applies always). Then you could click on the condition, and perhaps change the value in the project property file under that condition (almost like directly, a bit like search text functionality in VS). And if the entry would not exist, the editor would show what it would be adding to the project file, a bit like in Git Changes. It could even suggest typical conditions that people use such as:
Condition="'$(Configuration)|$(TargetFramework)'=='Debug|net9.0-ios'
Condition="$([MSBuild]::IsOSPlatform('windows'))"
Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'ios'"
Condition="$(TargetFramework.Contains('-android'))"
Condition="'$(TargetFramework)'=='net9.0-ios' or '$(TargetFramework)'=='net9.0-maccatalyst'"
Finally, the editor could run some summaries what the conditions mean in terms of various platforms, and also present default values if some relevant platform is not covered by the conditions.
Beta Was this translation helpful? Give feedback.
All reactions