Re: Resource Leak

"Goran" <goran.pusic@xxxxxxxxx> wrote in message news:eaf0f835-5187-4b03-9e93-287a2e9ef72d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
AFAIK, MS effectively says: "don't write shell extensions in .NET.
Instead, write a stub for the extension in native code, then call out
to a .NET *.exe". Problem being that (at the time I saw this, but
possibly now as well), only one instance of .NET runtime could run
within on process. But if extension A needs .NET version X, and
extension B needs ,NET Y, then what? Hence the advice.


With VS 2010 and .NET 4, you can now write shell extensions in .NET.


But said "split the extension" advice is sound for native code as well
- who wants his explorer.exe sucking in who knows how much stuff (for
all in-proc extensions system might have), when most of it is needed
for a couple of seconds, time to time?


Yup!

-- David

.