Message248417
> My py_auto_file association
Oh, it's that auto filetype again. Steve, when you say you fixed this for 3.5, does that means there's a simple command or API to revert this automatic ProgId back to the Python.File type? This problem shows up repeatedly on Stack Overflow, so it would be nice to have a solution that works consistently from Windows 7 to 10.
cmd.exe's built-in assoc and ftype commands only modify the local machine association and filetype. A per-user install doesn't use those, and sometimes Explorer instead uses a per-executable command defined in Software\Classes\Applications. Also, just modifying the command doesn't actually select what ShellExecuteEx will choose to run. I used to directly modify Explorer's FileExts\...\UserChoice for a given file extension, but that's actively discouraged by a deny ACL nowadays. Fine, but I've run into cases where Explorer's dialog doesn't let me choose a an existing ProgId. |
|
Date |
User |
Action |
Args |
2015-08-11 17:56:53 | eryksun | set | recipients:
+ eryksun, paul.moore, tim.golden, zach.ware, steve.dower, gladman |
2015-08-11 17:56:52 | eryksun | set | messageid: <1439315812.92.0.832965646535.issue24843@psf.upfronthosting.co.za> |
2015-08-11 17:56:52 | eryksun | link | issue24843 messages |
2015-08-11 17:56:52 | eryksun | create | |
|