run simple c++ exe on other system????

[Miguel]

I have a simple c++ program I just wrote with VC 6.0. I want to run this program on another machine, but it just locks up. What do I need to do to run the .exe file that is created in the debug folder on a different system?

thanks

[William DePalo [MVP VC++]]

"Miguel" <Mi****@discussions.microsoft.com> wrote in message
news:BD**********************************@microsof t.com...

I have a simple c++ program I just wrote with VC 6.0. I want to
run this program on another machine, but it just locks up.
What do I need to do to run the .exe file that is created in
the debug folder on a different system?

Well, do you have the development environment installed on the other
machine? Debug builds often use debug DLLs, if those DLLs are not present
the application should not run. I don't know why you have a lockup - perhaps
it is DLL hell (mismatch of application and DLL).

Note that I am specifically not addressing licensing issues - only you know
how many machines are licensed to run the compiler in your shop.

Regards,
Will

[Ronald Laeremans [MSFT]]

Yes, by building a release version. You will still need to deploy the
correct run time dlls though is you have selected the dynamic CRT or MFC,
but the release files you can legally redistribute.

Ronald Laeremans
Visual C++ team

"Miguel" <Mi****@discussions.microsoft.com> wrote in message
news:51**********************************@microsof t.com...

Thanks for the reply Will.

I do not have the development enviornment on the other machine. Is that
my only option to get this program running on that machine? Can I build
an executable that doesn't rely on debug dlls?

Thanks

"William DePalo [MVP VC++]" wrote:

"Miguel" <Mi****@discussions.microsoft.com> wrote in message
news:BD**********************************@microsof t.com...

> I have a simple c++ program I just wrote with VC 6.0. I want to
> run this program on another machine, but it just locks up.
> What do I need to do to run the .exe file that is created in
> the debug folder on a different system?

Well, do you have the development environment installed on the other
machine? Debug builds often use debug DLLs, if those DLLs are not present
the application should not run. I don't know why you have a lockup -
perhaps
it is DLL hell (mismatch of application and DLL).

Note that I am specifically not addressing licensing issues - only you
know
how many machines are licensed to run the compiler in your shop.

Regards,
Will

[Abhinaba Basu]

what do you mean by a simple application? Do you use MFC or any other
FrameWork or is it a place simple console application.

If you use frameworks like MFC then you would require to build the
application in release mode and then use it on the target machine. If you
use debug build then your application might use the debug versions of the
dll like say MFC42D.DLL for MFC4.2 instead or MFC42.DLL. Dubug dlls are not
present on systems which does not have development tools like VC++
installed.

However, if the above case were true then you should not have got lockups in
your application. You should have seen popup error messages telling you that
the dll was not found. Try eliminating other problems like uninitialized
variables, eliminate all warning in your build and other similar things.