wrote in message news:%23Bt7ug2qDHA.2416@TK2MSFTNGP10.phx.gbl...
> Hello everybody,
>
> I know that not very much people thinks that the upgrade of the vb6
> application is the way to go.
> But I have a big business application, with many customers, continuously
> developing new functionality, and I can't afford to stop the development
> with vb6, and begin again, with a new version in vb.net from the
beginning.
> I have read books and articles about refactoring, and I have convinced
> myself that this is the way for me.
> Well, now my questions:
> I have found that the upgrade wizard creates pairs of assemblies for some
of
> the dll's that it has to import.
> Example: AxInterop.AxMscommctlLib and Interop.MscomctlLib for the
"Microsoft
> Windows Common Controls" ocx, the same for stdole, and for the ocx
controls
> I uses (from ComponentOne in my case).
> But this is not the case for de MSADO dll.
>
> I would like to know the differences of the two assemblies. Which is the
> reason of these?
>
> Besides, I have a warning that tell me that I have a referenced component
> with a custom wrapper created newer for some of this assemblies, and the
IDE
> offers me to replace each one automatically.
>
> I think it is for the PIAs for Office XP that I have installed.
>
> But the problem is that the replacement doesn´t work.
> Even If I try to make the replacement manually, removing the assembly an
> installing the PIA following the instructions it doesn´t work.
> I don´t know how to use the PIAs in replacement for the assemblies created
> by the upgrade wizard.
> And Microsft recommend only to use PIAs for interop assemblies.
>
> Can somebody help, me giving some light to the problem? or can somebody
> point me to a place where I can read about this?.
>
> Thanks in advance.
> Juan M. Cervera
>
>

Juanma Cervera wrote:

> I would like to know the differences of the two assemblies. Which is the
> reason of these?

> can somebody point me to a place where I can read about this?.

"Christian Fröschlin" <froeschlin@mvtec.com> wrote in message
news:3FBB2BF8.5080103@mvtec.com...
> Juanma Cervera wrote:
>
> > I would like to know the differences of the two assemblies. Which is the
> > reason of these?
>
> The AxInterop assembly is for ActiveX control wrappers, the
> other one for plain COM classes. From the command line you
> would generate these using aximp and tlbimp, respectively.
> If you reference a library which does not contain ActiveX
> controls, only one assembly is generated.
>
> > can somebody point me to a place where I can read about this?.
>
> Useful links are collected at
>
> http://www.dotnetinterop.com/articles.aspx
>