RegAsm.exe missing from client machines

[Sean]

I've developed a VB6 application that uses a VB.Net dll. When
distributed to client machines it works fine except for a few cases.
The clients having problems seem to be missing RegAsm.exe from their
machines, and the .Net dll is not being registered correctly (no tlb
file is being created), causing an error saying "ActiveX cannot create
object" when trying to create an object from the type library. What do
the clients need to do to get regasm.exe on their machines? Is it
available for download somewhere, or do they need to install some other
program?

[schneider]

I think that is in the Client Framework directory, or may be only in the
previous version..
"Sean" <nb****@gmail.com> wrote in message
news:11*********************@g49g2000cwa.googlegro ups.com...

I've developed a VB6 application that uses a VB.Net dll. When
distributed to client machines it works fine except for a few cases.
The clients having problems seem to be missing RegAsm.exe from their
machines, and the .Net dll is not being registered correctly (no tlb
file is being created), causing an error saying "ActiveX cannot create
object" when trying to create an object from the type library. What do
the clients need to do to get regasm.exe on their machines? Is it
available for download somewhere, or do they need to install some other
program?

[Sean]

So can I simply send out copies of my regasm.exe to clients who need
it? Or should I be doing something with my VB.Net solution for the dll
that will cause regasm.exe to be installed on their machines?

[Herfried K. Wagner [MVP]]

"Sean" <nb****@gmail.com> schrieb:

So can I simply send out copies of my regasm.exe to clients who need
it?

No! Instead you need to install the .NET Framework, which is necessary to
execute the .NET DLL.

Deploying the .NET Framework in a setup package
<URL:http://dotnet.mvps.org/dotnet/faqs/?id=deployframework&lang=en>

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[Sean]

Thanks for all the help. I ended up just having the clients install
the .Net framework themselves, since there were only a few missing it.
Instructions are here for anyone else needing this fix:

http://msdn.microsoft.com/netframewo.../framework1_1/