and did you compile it in Release Mode (rather than debug mode)?
I think that might be the problem. Go to build --> Configuration Manager and select 'Release' instead of 'debug', close the window and press F5. You will now have a new sub-directory in your project's folder 'release' with the executable in it.
Regards Niek
[edit]
ps. Does your other PC have .NET Framework 2.0?
[/edit]
Nick Evan
Not a Llama
10,112 posts since Oct 2006
Reputation Points: 4,142
Solved Threads: 403
also the end user pc needs .NET Framework 2
jbennet
Moderator
18,523 posts since Apr 2005
Reputation Points: 1,826
Solved Threads: 601
that's not always enough. Special stuff is needed, which is only added by installer creators designed for Visual Studio 2005.
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337
doesnt the installer wizard automatcially add dependencied in VS2005?
jbennet
Moderator
18,523 posts since Apr 2005
Reputation Points: 1,826
Solved Threads: 601
Doesn't VC++ have an option to create a deployment or application wizard? With this you create a setup file and the DLLs needed are loaded into the target system.
WaltP
Posting Sage w/ dash of thyme
10,506 posts since May 2006
Reputation Points: 3,348
Solved Threads: 944
the application deployment wizard is under the project properties tab (where you set icons, startup form, compile options etc...)
you can add additional dependencies in this page
This wizard is cut down in express editon by the way so if your using that, your out odf luck
jbennet
Moderator
18,523 posts since Apr 2005
Reputation Points: 1,826
Solved Threads: 601