Final statement about managed shell extensions needed from MS

  • Thread starter Thread starter Patrick Philippot
  • Start date Start date
P

Patrick Philippot

Hi,

According to this discussion:

http://forums.msdn.microsoft.com/en-US/netfxbcl/thread/1428326d-7950-42b4-ad94-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.
 
If writing shell extensions in managed code is really unsafe, this would
be the first big design flaw that I encounter in .Net.
Click to expand...

Why would that be a design flaw? .Net isn't actually supposed to be
everything to everyone. It's merely supposed to be many things to most
people. I'm hard pressed to believe we'll ever have a one size fits all
language and platform.

As to official word, what would you consider official? Every MS employee
I've seen comment on it has said not to do it. That article you mentions has
Jesse Kaplan (one of the CLR program managers) and Raymond Chen (on the
Windows Shell team) agrees later in the comments. That's official enough for
me.

Andrew Faust
 
Back
Top