diff --git a/docs/index.md b/docs/index.md index 211fa9df..6567a092 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,7 +1,7 @@ --- title: Windows Midi Services layout: home -has_children: true +has_children: false --- # Windows MIDI Services diff --git a/docs/troubleshooting/type-initialization-error.md b/docs/troubleshooting/type-initialization-error.md index 2da8b2be..c58aada5 100644 --- a/docs/troubleshooting/type-initialization-error.md +++ b/docs/troubleshooting/type-initialization-error.md @@ -4,14 +4,8 @@ title: Type Initialization Error at Runtime parent: Troubleshooting --- -# Troubleshooting +# Type Initializer Error -## Errors - - -### Type Initializer Error - -If you receive the error "The type initializer for `Windows.Devices.Midi2.` threw an exception", 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 do run the installer which puts the appropriate activation entries into the registry. - -This should never appear in production when Windows MIDI Services is in the box, unless you are using a development build for which the newer types have not been properly registered. +If you receive the error "The type initializer for `Windows.Devices.Midi2.` 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. +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.