Shell Extensions (.NET)
Posted by jpluimers on 2020/06/04
Over time it seems that Shell Extensions (.NET) [WayBack] have become possible.
In the past this was recommended against because Shell Extensions can be loaded by any process having a file dialog open, even if these did not expect .NET framework(s) to be hosted in-process.
It looks like that restriction has been alleviated with .NET 4.x where it is possible to in-process host multiple .NET frameworks: [WayBack] CLR Inside Out: In-Process Side-by-Side
Related:
- [WayBack] Create a Shell Extension Handler thumbnail extractor with .net? (new location of old WayBack: Create a Shell Extension Handler thumbnail extractor with .net? – MSDN Forums)
- Seems not relevant any more: [WayBack] Don’t do Shell Extension Handlers in .NET – Junfeng Zhang’s Musing
- [WayBack] c# – detect Windows Explorer copy operation – Stack Overflow
- [WayBack] winapi – Is it safe to block in callback of CopyFileEx? – Stack Overflow
- [WayBack] Any takers? The Windows API function CopyFileEx allows a callback function to be specified which is then being called when a part of the file has been … – Thomas Mueller (dummzeuch) – Google+
- [WayBack] CopyFileEx function (Windows)
–jeroen
The Wiert Corner - irregular stream of stuff 
Leave a comment