Managed extensions for older VS

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Pavel Novak - 24 Oct 2004 23:37 GMT

Hi,
is it possible to make managed extensions created in VS 2005 working in
older versions VS 2003, 2002?
I'm trying to do this with Project sample included in VSIP 8.0 and VS2003,
it has registered properly, but while trying to create the project VS says
that .myproj is not installed.

I checked the registry, Project is installed, but there is under
Packages/<GUID> key:
Class: Microsoft.VisualStudio.VSIP.Samples.Project.MyPackage
CodeBase: <path>\VSIP8.0\EnvSDK\CS_Samples\Project\bin\Debug\Project.dll
InprocServer32: C:\WINDOWS\system32\mscoree.dll

I made unmanaged new project type for VS2003, there was the package DLL path
under InprocServer32. Are these entries compatible with VS2003? If not, is it
possible to run this example in it?

Thanks a lot,
Pavel

Reply to this Message

Gaston Milano - 26 Oct 2004 15:34 GMT

You should do some extra work if you wanna create a project system on
VS2003, there is a problem in VS2003 if you wanna create a full managed
project system. Some time ago Allen explain this problem in his weblog
http://weblogs.asp.net/allend/archive/2004/02/11/71552.aspx

Regards,
Gaston

> Hi,
> is it possible to make managed extensions created in VS 2005 working in
[quoted text clipped - 15 lines]
> Thanks a lot,
> Pavel

Reply to this Message

"Ed Dore [MSFT]" - 28 Oct 2004 18:14 GMT

Hi Pavel,

Our VSIP compatibility story is a bit mixed. Unmanged/native packages
should be compatible. The goal is for our IDE platform interfaces to be
binary compatible, but there are some exceptions, such as the debugger team
changing and reguid'ing their interfaces for debug engines due to some
needed security changes. Outside of a small number of exceptions, and
unmanaged/native VSIP package written for VS2003 should also run in VS2005.
You could also backport a VS2005 package, provided you either code to the
VS2003 interfaces, or write your package to conditionally use the VS2005
specific features only when hosted in VS2005.

For managed packages, the platform interfaces and corresponding interop
assemblies are identical between VS2003 and VS2005. So a managed package
written directly to the interop assemblies can be made to work in both
VS2003 and VS2005. However, a managed package using the new managed package
framework (basically the VS2005 replacement for the VSIP Helper dll), will
only work on VS2005. This is because the managed package framework
assemblies are built with our VS2005 toolset, and a 2.0 managed assembly
cannot be loaded into VS 2003.

So if you want to build a VSIP package that will target both VS2003 and
VS2005 you'll want to either stick with an unmanaged package, or avoid the
VS2005 managed package framework, and build your package with VS2003. Note,
you can still utilize the VSIP Helper assembly from VS2003, and run the
package under VS2005.

Sincerely,
Ed Dore [MSFT]

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

Reply to this Message

Bill Korbecki - 15 Jul 2005 22:24 GMT

Hi,

The previous postings talked about VS 2003 and VS 2005 interop, but didn't
mention anything about 2002. Since the VS 2003 SDK is indicated as usable
for VS 2002 as well are the managed interop packages also meant to work with
VS 2002?

Out of curiosity, I tried it out and found that if I rebuilt the VSIP helper
assembly to use the VS 2002 version of “Microsoft.VisualStudio.dll” it seemed
to work.

1: Assuming the helper assembly is rebuilt referencing the older version of
“Microsoft.VisualStudio.dll”, does that create a viable working scenario for
a VS 2002 managed package or will there be unforeseen problems that I have
not run into yet?

2: Will the interop assemblies (which I cannot rebuild) function properly
for VS 2002? It seems to be working in my case, but are there other cases I
should be concerned about?"

Thanks in advance,
Bill

Reply to this Message

Managed extensions for older VS

Free Magazines