For full discussions on the issue see these: https://stackoverflow.com/questions/51219062/uwp-usb-hid-device-wont-connect and https://github.com/tpn/winsdk-10/blob/master/Include/10.0.16299.0/winrt/AppxManifestTypes.xsd
To recreate the problem, open a package manifest and paste this XML in the capabilities section:
<Device Id="vidpid:2B24 0001">
<Function Type="usage:0005 *" />
<Function Type="usage:FF00 0001" />
<Function Type="usage:ff00 *" />
YES YES 100x YES!!!!
171 votes27 comments · Universal Windows Platform » XAML/Controls/Composition · Flag idea as inappropriate… · Admin →
With the announcement and preview release of WinUI Nuget package, we are able to release and update XAML controls independent of OS Updates. We also design controls for backwards compatibility. We’ve listened to customer feedback based on our initial implementation, one being to enable backwards compatibility. Due to this feedback, we are adjusting the implementation to include Input Validation inside the WinUI Nuget Package. We are hopeful to release a backwards compatible version of Input Validation in calendar year 2019.
Thanks Harini! Glad to hear this because I know that you're trying to make XAML as standard as possible across the board so hopefully the solution will use INotifyDataErrorInfo like the other platforms.
This item is too broad. Specifically, Microsoft needs to implement functionality on UWP controls so that when an object is bound to a control, and that object implements INotifyDataErrorInfo, the control should listen to error changes, and display them accordingly. This is excellent functionality in Silverlight and WPF.
This feature is clearly necessary. As mentioned here, we can dynamically load assemblies on iOS, and Android with Xamarin. Why can't we do the same with UWP?
Get on this Microsoft!!!!
5 votes0 comments · Universal Windows Platform » Dev Center + Microsoft Store · Flag idea as inappropriate… · Admin →