foobar2000 | kode54 's foobar2000 components

I believe ASSOCF_OPEN_BYEXENAME:ASSOCSTR_EXECUTABLE searches HKEY_CLASSES_ROOT\Applications.

ShellExecuteEx searches the "normal directories" and the App Paths key:

Finding an Application Executable

When the ShellExecuteEx function is called with the name of an executable file in its lpFile parameter, there are several places where the function looks for the file. We recommend registering your application in the App Paths registry subkey. Doing so avoids the need for applications to modify the system PATH environment variable.

The file is sought in the following locations:

• The current working directory.

• The Windows directory only (no subdirectories are searched).

• The Windows\System32 directory.

• Directories listed in the PATH environment variable.

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths

(HKEY_CURRENT_USER is also used on recent versions of Windows)

The Assoc API is more focused on file associations.

If you are just going to execute the file then you should just use ShellExecuteEx. If you just want to find the fully qualified path you can use some helper functions to do some of the work for you:

FindExecutable seems promising but it has some compatibility workarounds and it will also find the executable used to open registered types (c:\foo\bar.txt might resolve to c:\Windows\Notepad.exe etc. because it uses ASSOCSTR_EXECUTABLE),

If you want to look for extensions like .exe and .bat automatically you can use PathResolve(..., PRF_REQUIREABSOLUTE|PRF_VERIFYEXISTS|PRF_TRYPROGRAMEXTENSIONS|PRF_DONTFINDLNK) but you must be careful that the search string does not contain \ nor :.

If you only want to look for a .exe you must manually append the extension if it is not present and then call PathFindOnPath(, NULL).

Neither of these functions looks in the App Paths key, they do not use the exact same search order as ShellExecuteEx (system32 before %windir%?) and they are most likely limited to MAX_PATH.

If those functions (or your own equivalent version) fail then you can check the App Paths key. When reading from the registry you must append .exe if there is no extension and use a helper function like SHQueryValueEx that will expand REG_EXPAND_SZ strings.

You need to use AudioManager class as below, whenever u need audio focus, call below method

/D sets the working folder instead of the program to run - see help start.
Try
start /d "c:\program files\mpc-hc\" "c:\program files\mpc-hc\mpc-hc64.exe" "%temp%\hoard.m3u"

At least with a ListView control, there is some limited built-in support provided by way of the InsertionMark property, but this only works in icon view, small icon view, and tile view. It doesn't work when the Items are sorted or when groups are turned on, and it requires comctrl32.dll version 6 (thus meaning Windows XP or later, with Visual Styles enabled).

If you want a more general solution, you can easily draw a line yourself in the DragOver event:

To avoid flicker we remember the last index:

executed in cmd && is recognized as a command separator, but in registry may be taken as a litteral argument "&&". maybe following can help

I've found a solution, and my problem lied in the way I set it to listen for dragging.

Instead of using common sense and listening for actual drags, I instead listened for a "Mouse Release" (i.e, drag and release causes it to update the value to the released point) but this didn't do me any good, and caused the lag in the gif above.