Microsoft-ui-xaml: Need workaround for removing Shadow from controls for project built with SDK version < 1903, but project deployed to devices running Windows 1903

[Skynet094]

Hi, I am trying to remove shadow from a CommandBar, that initially did not have any MenuFlyout for the OverflowButton (More-button), it had SecondaryCommands, however there was this issue of shadow around the pop up, as the Popup is has a large corner radius (26px) it looks bad with shadow. So we don't want it. Also, we have several content dialogs, from which we were able to remove the shadow from, using a rather ugly hack.

I am aware of the ""IsDefaultShadowEnabled" property fix, however as the Target build version of our project is 1809, that property is not available to us. Can anyone here please tell me a workaround for getting rid of Shadows from xaml controls when we not building with 1903, but our app is to be deployed in devices running windows 1903 too (min target is 14393)?

At this point, a workaround for removing shadow from MenuFlyout given the context could be really, really helpful.

The QA team associated with our project isn't accepting that it's a platform issue. Any help would be much appreciated.

As to the question, why we are not using build target 1903, one of the reasons is, it's because it causes a lot of unrelated unwanted issues.

[adrientetar]

Isn't that what conditional XAML is for?

[Skynet094]

Conditional xaml is available for when the min version of the project is 15063. For our case it's slightly lower , 14393.

But that's not the issue, I can use ApiInformaion to know whether the property exists before applying .

Our issue is our target build version is not 1903. Where that property is exposed. But our app will run on devices that run windows version to 1903 (this is where the shadow issue comes up).

The decision to make 1809 as target version was set a long time ago.

[adrientetar]

Then the only way would be to use reflection if that works, there's no magic here.

[Skynet094]

I feel like you are not getting the issue. Obviously not expecting any magic.

[jevansaks]

@Skynet094 can you elaborate on why you can't target 1903? Is there a limitation with your build environment?

[Skynet094]

We moved to using SDK version 1903

[Skynet094]

@Skynet094 can you elaborate on why you can't target 1903? Is there a limitation with your build environment?

No, there wasn't any issue, we are using Visual Studio 2017. The senior members in the team I work in were reluctant to move to 1903 SDK as after building with SDK 1903, some additional issues arose, for instance, the commandbar's menuflyout started having a weird background but only when deployed to 1809 devices, there were some other issues, but we fixed them and then the management gave us the go. Thanks for reading!

[jevansaks]

Oh ok! I was going to say that if it's quirks related (such as you might have been seeing) you can have your target SDK be 1903 (to let you use new APIs) but still set your MaxTestedVersion to 1809 to make the runtime behavior the same as before.

[Skynet094]

Thank you! I will use that information.