Re: DOTNET-PRODUCTS Digest - 17 Nov 2002 to 18 Nov 2002 (#2002-53)

Correct Jim. You do need VSIP to implement custom editors. When this
(someday) gets revamped for managed interfaces (VSIP), maybe they will
refactor it. Who knows?

----------------------------------------------
Sam Gentile
Microsoft .NET Consultant
http://www.samgentile.com/
Read my .NET Blog at http://radio.weblogs.com/0105852/



-----Original Message-----
From: dotnet-products [mailto:[email protected]] On
Behalf Of Jim Murphy
Sent: Tuesday, November 19, 2002 11:09 AM
To: [email protected]
Subject: Re: [DOTNET-PRODUCTS] DOTNET-PRODUCTS Digest - 17 Nov 2002 to
18 Nov 2002 (#2002-53)

> I can personally vouch for Francis' product - it rocks!

I like it too!


> there are about 10 things that can be done only with VSIP
> and not the Automation model (add-ins) like be on the VS splash
screen,
> etc but there is a whole lot that can be done with the automation
model.
> ... you can use an add-in unless you need to be on the
> splash screen, custom editor type, custom project hierarchy, etc.

I have lots of ideas that mostly involve adding custom editors to
VS.NET.  As far as I understand it that's not possible with Addins.

In a perfect world I would like to add a customer editor, associate it
with a file type,provide a selectable view aka ASP.NET
designer/codebehind where I can write the designer view and delegate to
existing VS.NET editors for other views.  Heck, while I'm dreaming, I'd
like to write the customer designer view in Winforms.

:)


Jim