I have a VB6 application which now uses a VB.Net COM object, so the framework
is now needed. I ran across which file to place in the bootstrap but can't
find it again.
I think all I need to do is place the .Net 2.0 redistrib exe in the
bootstrap but want to check first. My concern is how will the older
installer know about the dependency?
Thank you
MikeD - 19 Feb 2008 21:49 GMT
>I have a VB6 application which now uses a VB.Net COM object, so the
>framework
[quoted text clipped - 5 lines]
> bootstrap but want to check first. My concern is how will the older
> installer know about the dependency?
You should ask this in a .NET newsgroup as they're the people who are going
to be most helpful in ways to distribute the .NET Framework. Your issue
really doesn't have anything to do with VB6 (which is what this newsgroup is
for).
FWIW, my recommendation would be to make the .NET Framework a prerequisite
and instruct users to obtain it from Windows|Microsoft Update.

Signature
Mike
Microsoft MVP Visual Basic
Jan Hyde (VB MVP) - 20 Feb 2008 09:06 GMT
BigJohn <bigjohn@newsgroup.nospam>'s wild thoughts were
released on Tue, 19 Feb 2008 07:40:00 -0800 bearing the
following fruit:
>I have a VB6 application which now uses a VB.Net COM object, so the framework
>is now needed. I ran across which file to place in the bootstrap but can't
[quoted text clipped - 3 lines]
>bootstrap but want to check first. My concern is how will the older
>installer know about the dependency?
It probably won't but there is nothing to stop you adding it
in.
--
Jan Hyde
https://mvp.support.microsoft.com/profile/Jan.Hyde
anup - 08 Apr 2008 17:29 GMT
i am also facing the same problem.. could you find any solution for the problem
> I have a VB6 application which now uses a VB.Net COM object, so the framework
> is now needed. I ran across which file to place in the bootstrap but can't
[quoted text clipped - 5 lines]
>
> Thank you
BigJohn - 21 Apr 2008 18:06 GMT
No. We are unsuccessfully trying to work through this. Step-by-step
instructions were at one time available, but with VB6 soon retirement, I
think it was pulled.
When .Net came out, there were quite a few interoperability instructions.
Guess upgrading is the only option at the moment.