This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 28.000000000000004%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESA%3C/text%3E%3C/svg%3E)
We are porting our UI from Win Forms/WPF to WinUI3 C#. My classes to connect and control industrial cameras like Basler and IDS usb3 versions work as expected in WPF. But I am unable to connect to them when using WinUI3. All of the problems (the errors aren't the same) seem related to threading. I converted my camera class to .Net Standard 2.0. That made no change (works on WPF fails on WinUI3).
This is errors from my Immediate Window:
Exception thrown: 'System.Runtime.InteropServices.SEHException' in Basler.Pylon.dll
Exception thrown: 'System.Runtime.InteropServices.SEHException' in Basler.Pylon.dll
Exception thrown: 'System.Runtime.InteropServices.SEHException' in Basler.Pylon.dll
Basler.Pylon
External component has thrown an exception.
at Pylon.CDeviceInfo.{ctor}(CDeviceInfo*)
at Basler.Pylon.Camera..ctor()
at Detectors.Camera_Basler_USB3.Connect()
I have updated to the latest drivers for both Basler and IDS.
Hello @Scott Alexander ,
Welcome to Microsoft Q&A!
This issue seems to be more related to third-party drivers. It is recommended that you report this issue to the camera driver vendor.
Thank you.
It is not their drivers. That is an easy, non-rigorous stance to take. (We have reported this to the vendors by the way). But ...
All of the cameras work when using the WPF framework. It is only when using WinUI3 that they fail. We have even compiled .Net Standard 2.0 wrappers for the cameras into DLL that are then referenced by a WinUI3 UI and they fail.
Microsoft has changed access, etc. that prevents the interaction.
Furthermore, I haven't been able to find any guidance from Microsoft on this. And I suspect, based upon all the 'hoop jumping' I've had to do to get other standard tasks (like catching the left mouse button pressed event) to work in WinUI3 that the framework has not been finished.
Can you please point me to the Microsoft standard, requirement, etc. that I can then forward to our vendors so that they can overcome the WinUI3 limitations? They currently don't see any market need to be compatible with WinUI3. If it is truly the future for Microsoft, then it is important to make their work easy ... I think.
Hello @Scott Alexander ,
You can try to open a support ticket, but I can't guarantee that the ticket will not be rejected due to third-party API reasons, but you can try it.
you can open a support ticket at link below:
Please select Developer Tools -> Windows SDK -> Windows APP SDK -> WinUI 3 in the support page and you could contact the team. Please kindly note that your support ticket will be free if it is Microsoft's issue.
Thank you
Did you check if the MS sample about camera capture works ?
https://github.com/microsoft/Windows-Camera/tree/master/Samples/MediaCaptureWinUI3
Thanks ... I'm trying to get that sample to run; but so far, there are many problems getting it to compile (and yes, I did the unblock thing for unzipping). This is the second error I've found so far.
... and based upon some copilot troubleshooting, I suspect that the windowsappsdk is broken and doesn't handle the COM components as expected. I've updated to the latest version and can't even compile. Heres what points me there:
Windows App SDK Runtime:
This sample works on my PC (I have no webcam but I use virtual cameras to do tests)
When running in an unpackaged app, you must add in the .csproj
<WindowsPackageType>None</WindowsPackageType>
That got the sample app working. Recognizes/finds my webcam; but, not my Basler camera. I doubt it is a windows.devices camera and so not found.