In general, a VB.NET exe or DLL (is it a class library?) just need the .NET
framework, but you've got COM errors and you haven't explained where COM
fits into your programs. Your DLLs are class libraries that are doing .NET
Interop? Or are they trying to create some other COM object that is not
provided by one of your DLLs? If you're installing .NET interop DLLs, look
at regasm.exe. If you're trying to create some other external COM object,
you may need to install the interop DLL for that COM server.
--
Phil Wilson
[MVP Windows Installer]
Definitive Guide to Windows Installer
http://www.amazon.com/exec/obidos/tg...044380-4696760
"Matt" <(E-Mail Removed)> wrote in message
news:2C402DA0-2FE6-47EC-80D6-(E-Mail Removed)...
> I created some DLL and EXE files in VB.NET to be used on a Windows XP
computer. They worked successfully on my laptop where they were written, so
I prepared another machine to use them. I installed dotnetfx.exe on the
other machine and registered the DLL's. When I tried to run the DLL's,
however, I got this message:
>
> "Attempt to execute COM object [object name here] failed. Could not
create object."
>
> When I tried to run the EXE files, this this was the message:
>
> "Application has generated an exception that could not be handled.
Process id=0xd08 (3336), thread id=0x408 (1032)"
>
> Are there certain steps to place .NET DLL's and EXE's on another Windows
XP machine?
>
> Thanks in advance,
> Matt
Similar Threads
