![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | Final statement about managed shell extensions needed from MS Hi, According to this discussion: http://forums.msdn.microsoft.com/en-...-8e962124043e/ it is very unsafe to write shell extensions in managed code (and I can understand why). However, Microsoft themselves are providing such extensions and are giving examples in the SDK. So what? I have to make a design decision about a new product and I'm rather puzzled by this. If writing shell extensions in managed code is really unsafe, this would be the first big design flaw that I encounter in .Net. Thanks in advance. -- Patrick Philippot MainSoft Consulting Services www.mainsoft.fr |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Can parent shell monitor run/crash status of Child shell/exe ? | PowerShell | |||
| Writing Shell Extensions / Extending Explorer Context Menu - XP 64 | .NET General | |||
| Windows Explorer Shell Extensions | Vista General | |||
| Explorer.exe shell extensions and switches | Vista General | |||
| Per-user shell context menu extensions? | Vista security | |||