Work around UIKit/UIKit.Xaml namespace collision issue; full fix will come in a subsequent fix next month.
Work around UIKit/UIKit.Xaml namespace collision issue; full fix will come in a subsequent fix next month.

Background:
Apps that reference UIKit.winmd (generated by UIKit.Xaml.dll) can run into missing Xaml type info in their packages, due to a namespace collision with UIKit.Xaml.dll (who's root namespace is 'UIKit') and UIKit.dll (who's root namespace *also* 'UIKit').

Depending upon the build ordering, *either* the resources for UIKit.dll *or* UIKit.Xaml.dll are generated as the on-disk UIKit.pri file that is pulled into apps referencing UIKit.Xaml.dll's UIKit.winmd.  This causes issues such as missing text on the buttons in our UIActionSheet implementation.

The short-term fix is to change UIKit.dll's root namespace to 'UIKit.ObjC' (which doesn't appear to cause any issues), but long-term we should probably change UIKit.Xaml's root namespace to match its binary name (UIKit.Xaml), which would result in it generating a UIKit.Xaml.winmd, UIKit.Xaml.pri, etc.  The longer-term fix will require churn across all of UIKit.Xaml in order to align with the new root namespace, which will also affect the Nuget we generate for middleware usage.

nathpete-msft/WinObjC,nathpete-msft/WinObjC,pradipd/WinObjC,Microsoft/WinObjC,bbowman/WinObjC,ehren/WinObjC,nathpete-msft/WinObjC,vkvenkat/WinObjC,vkvenkat/WinObjC,nathpete-msft/WinObjC,pradipd/WinObjC,ehren/WinObjC,bbowman/WinObjC,ehren/WinObjC,pradipd/WinObjC,vkvenkat/WinObjC,nathpete-msft/WinObjC,Microsoft/WinObjC,vkvenkat/WinObjC,ehren/WinObjC,pradipd/WinObjC,pradipd/WinObjC,bbowman/WinObjC,Microsoft/WinObjC,bbowman/WinObjC,Microsoft/WinObjC,bbowman/WinObjC,ehren/WinObjC