Add-in to VSIP package conversion basic questions

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Sergey M - 22 Nov 2004 14:53 GMT

Hi all,

I have a pretty extensive add-in that relies heavily upon VS.NET code
model. I access the code model through the EnvDTE of course. I plan on
migrating the add-in to VSIP in the near future (using managed
extensions).

I'm wondering about the direction I should take. Should I reference
EnvDTE.dll assembly in VSIP package in order to reuse most of the
existing code? Or, is there set of equivalent VSIP code model services
to work thought? I'd appreciate your feedback.

BTW, does anyone know whether VSIP managed extensions support is
currently available or perhaps planned for Whidbey beta?

Thanks in advance.

Signature

Sergey M
http://www.usysware.com/dpack/

Reply to this Message

Steve Maillet (eMVP) - 22 Nov 2004 17:32 GMT

1) Why switch? If it's working as an Add-In what do you expect to gain from
VSIP?
2) Yes, There is a managed extensions for Whidbey beta available at the VSIP
web site.

Signature

Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com

Reply to this Message

Sergey M - 22 Nov 2004 17:49 GMT

Steve,

> 1) Why switch? If it's working as an Add-In what do you expect to gain
> from VSIP?

I'm afraid I've reached the limit of what can be done with one of the
add-ins. VSIP would (supposedly) allow me to advance my product beyond
the add-in limitations. There are also few minor things, like splash
screen product icon for example, that I'd like to add to my
distribution.

So, the question still remains. Should I use EnvDTE in my VSIP package
or some VSIP service(s), and which is the right way to go about it?

> 2) Yes, There is a managed extensions for Whidbey beta available at
> the VSIP web site.

That's good to know regarding managed extensions for Whidbey. Do you
happened to know if October 2004 Preview available for download includes
that?

Thanks for your help.

Signature

Sergey M
http://www.usysware.com/dpack/

Reply to this Message

Steve Maillet (eMVP) - 22 Nov 2004 19:15 GMT

Whether you use EnvDTE in a VSIP component depends entirely on what it is
you are doing. If it was me I'd leave as much of the current code base in
tact using the DTE and add new functionality via VSIP support. Tough to say
much more without any real details of what your code does or you are
planning.

The VSIP managed code support is part of the VSIP support for Whidbey (just
one download for managed and unmanaged) VSIP is a separate download from the
actually Whidbey download itself.

Signature

Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com

Reply to this Message

Sergey M - 22 Nov 2004 19:57 GMT

Steve,

> Whether you use EnvDTE in a VSIP component depends entirely on what it
> is you are doing. If it was me I'd leave as much of the current code
> base in tact using the DTE and add new functionality via VSIP support.
> Tough to say much more without any real details of what your code does
> or you are planning.

My add-in "walks" the solution, retrieves the projects collection,
interrogates each project's file code model via DTE. I was just
wondering if VSIP approach for using code model is to go through DTE or
perhaps use some other service. Take a look at this screenshot too see
what I get out of the DTE:

http://www.usysware.com/dpack/screenshot_cbr.htm

I keep on asking because I'm not entirely clear as to what the right
approach is. Is there separate code model access approach in VSIP? Or do
people always use DTE for that regardless whether that's an add-in or a
package it pertains to? Thanks.

Signature

Sergey M
http://www.usysware.com/dpack/

Reply to this Message

"Ed Dore [MSFT]" - 22 Nov 2004 23:42 GMT

Hi Sergey,

It's perfectly acceptable (and in some cases necessary) to utilize the DTE
automation support from a VSIP package.

There is no additional access to the code model stuff (at least nothing
I've seen). There an old Dr. eX blog at
http://blogs.msdn.com/dr._ex/archive/2004/03/09/86972.aspx, that talks
about accessing the DTE automation service from a VSIP package. It's a step
by step article for C++/ATL VSIP packages.

For managed packages, the following link is probably what you'd want.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechar
t/html/automation_walkthrough.asp

Sincerely,
Ed Dore [MSFT]

This post is 'AS IS' with no warranties, and confers no rights.

Reply to this Message

Sergey M - 23 Nov 2004 00:19 GMT

Ed,

> It's perfectly acceptable (and in some cases necessary) to utilize
> the DTE
> automation support from a VSIP package.

That's exactly what I was looking for. Thank you and Steve for helping
me with all of these questions.

Signature

Sergey Mishkovskiy
http://www.usysware.com/dpack/

Reply to this Message

Add-in to VSIP package conversion basic questions

Free Magazines