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)
With help on another question, I've been able to connect to my industrial camera and display an image. But I've only been able to do that by starting using the MediaCaptureWinUI3 sample project. I have tried to see what is special about it to see what I'm missing; but, have been unsuccessful.
So I believe there are other special settings in some of the support files that are enabling the functionality.
I made some tests based on https://learn.microsoft.com/en-us/windows/apps/develop/camera/camera-quickstart-winui3
and I did not meet any problem (in an unpackaged app, on Windows 10 22H2, Windows App SDK 1.6.241114003))
That works to expose the webcam. I followed the app note and it worked fine. But, there is some other secret sauce that the sample application has somehow turned on that allows my Basler camera to connect. It is not a webcam and doesn't comply with the DeviceInformation standard. It doesn't have a video stream. It provides a stream of frames (if that is pertinent).
I get this unhandled exception: Exception thrown: 'System.Runtime.InteropServices.SEHException' in Basler.Pylon.dll