Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

.exe files

Status
Not open for further replies.

Casbah

Programmer
May 18, 2004
31
IE
if i create e .exe program file using c++ and it works on one computer...why doesnt it work when i transfer it to another?
 
maybe it uses some dinamically linked libraries.
use this Depends.Exe to see which ones are required:


Ion Filipski
1c.bmp
 
A generic question gets a generic answer:
Because it is dependant on stuff that exists on the "one" computer but not on the "another".

If you use the Dependency Walker (a VC6 tool) on the "another" computer you can get a fairly clear picture of whats missing. Note that you should only distribute release builds. You are usually not licensed to distribute Microsoft's debug libs.

/Per

"It was a work of art, flawless, sublime. A triumph equaled only by its monumental failure."
 
ok i see the problem. because i built the program using visual studio.net it is now absolutely useless on any computer that doesnt have the .net framework. pretty obvious really, but it never occured to me that this technology would not be back compatable. I just dont see the point. I thought the point of .exe was its portability
 
>I thought the point of .exe was its portability

What it requires to run...well...it requires to run.

Besides, you're going from "exe built on new platform running on old platform" and you cant really assume that should always work.

However, one could assume that the other way "exe built on old platform runnin on new platform" should work. And M$ tries to adhere to this (thats why we've lived with 16bit compatibility for so long).

/Per

"It was a work of art, flawless, sublime. A triumph equaled only by its monumental failure."
 
Another thing...

>I thought the point of .exe was its portability

How portable it is is up to you, its developer, to decide.

Haven't played with .net myself but I'd assume (or hope) there's some way to make an app totally self-contained statically linking everything.

/Per

"It was a work of art, flawless, sublime. A triumph equaled only by its monumental failure."
 
you should install .NET framework to run .NET applications

Ion Filipski
1c.bmp
 
There is no way to provide a complete .exe file in .net (ie one that links in the .net framework).

People have asked for the facility for a proper linker in .net but M$ refuse, citing security,

M.

Hollingside Technologies, Making Technology work for you.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top