> Every time I try to run my EXE on any other machine than my development
> machine I get the following error.
[quoted text clipped - 10 lines]
>
> Randy
When you refer to "deployment", do you mean simply copying files from your
development machine to a target PC which has the .NET Framework installed,
but no Visual Studio? That is not going to work for you. You need to add a
Setup Project to your VB.NET solution and build an installation package to
export to target PC's. For more information on setup and deployment
projects, and application deployment in general, I recommend you start in
your MSDN Help. Start by searching on "setup and deployment" (no filter).

Signature
Peter [MVP Visual Developer]
Jack of all trades, master of none.
J L - 23 Jun 2005 20:40 GMT
Peter,
Why do you say copying wont work. I do it with my apps. As long as he
does not use ActiveX compoenents that require registering and as long
as he copies any DLL's that he might need, it should work. Or at least
it does for me. I thought that is what everyone meant by XCOPY
deployment.
John
>> Every time I try to run my EXE on any other machine than my development
>> machine I get the following error.
[quoted text clipped - 18 lines]
>projects, and application deployment in general, I recommend you start in
>your MSDN Help. Start by searching on "setup and deployment" (no filter).
Peter van der Goes - 24 Jun 2005 18:33 GMT
> Peter,
> Why do you say copying wont work. I do it with my apps. As long as he
[quoted text clipped - 4 lines]
>
> John
I may have misinterpreted what the OP said. I thought he'd tried to copy
only the .exe.