Merge pull request #322 from microsoft/pete-dev

vcpkg support for libmidi2

build/staging/version/BundleInfo.wxi

@@ -1,4 +1,4 @@
 <Include>
   <?define SetupVersionName="Developer Preview 6 arm64" ?>
-  <?define SetupVersionNumber="1.0.24109.1831" ?>
+  <?define SetupVersionNumber="1.0.24109.2304" ?>
 </Include>

docs/troubleshooting/minimum-requirements.md

@@ -0,0 +1,20 @@
+---
+layout: page
+title: Minimum Requirements
+parent: Troubleshooting
+---
+
+# Minimum requirements
+
+Windows MIDI Services will run on the latest supported 64 bit desktop versions (Arm and Inte/AMD) of Windows 11 as well as (after version 1.0 release) the latest supported version of Windows 10.
+
+TODO: Get exact minimum versions once we are in-box.
+
+MIDI 2.0 requires updates to the USB stack to support the new class driver assignment as well as to support the new framework used for creating the USB driver. In addition, the API, service, plugins, and apps all have a minimum Windows SDK requirement of 10.0.20348.
+
+There is no support for the following:
+- Older versions of Windows 10 or Windows 11
+- 32 bit operating systems
+- Xbox, Hololens, IoT Core (full IoT SKUs are supported per above version requirements), Surface Hub
+
+If your application is run on an unsupported operating system which does not have Windows MIDI Services installed, your first call into the API will fail with a type activation/invokation exception because there is no code running behind that metadata and no matching types in the registry.

docs/troubleshooting/type-initialization-error.md

@@ -6,6 +6,6 @@ parent: Troubleshooting
 
 # Type Initializer Error
 
-If you receive the error "The type initializer for `Windows.Devices.Midi2.<some class>` threw an exception" at runtime, in the console app in particular, it usually means that the Windows MIDI Services API is not properly registered on the system. This can happen during development if you don't run the installer which puts the appropriate activation entries into the registry.
+If you receive the error "The type initializer for `Windows.Devices.Midi2.<some class>` threw an exception" at runtime, in the console app in particular, it usually means that the Windows MIDI Services API is not properly registered on the system, or you are running on an unsupported version of Windows. This can happen during development if you don't run the installer which puts the appropriate activation entries into the registry.
 
-This should never appear in production when Windows MIDI Services is in Windows, unless you are using a development build for which the newer types have not been properly registered.
+This should never appear in production when Windows MIDI Services is in Windows, unless you are using a development build for which the newer types have not been properly registered, or you are running on an unsupported version or SKU of Windows.