[ToyMachine809]

I am a highschool programmer, and I had a Language arts project that I wrote in Visual C++. Its a jeopardy game for every label you click a question pops up in a message box. The problem occurs when I take it to put it on my Teacher's computer and it says I should "Consider re-installing the application", I put it on the desktop, once with just the exe, and again with the entire project. Is there any way I can fix this error? The only thing I can possibly think that might be wrong is that she maybe missing the .NET frame work, any help is very appreciated

[KYA]

Assuming its a windows machine and you are only transferring the .exe to show the final product, there shouldn't be an issue.

Are there some. dlls you reference in your code? If so then that might be the issue if the school computer doesn't have all the libraries and such installed.

[skater_00]

First of all, make sure you compile your program as a Release version, no Debug. Once you've done that, try to open the executable file again on the client machine.

Adding to what KYA said: You have to provide the required .dll files in your application folder if you are using .dll references in your code. Not all computers have all libraries installed. You can find .dll files very easily by using a search engine.

If it still doesn't open, try the following:

I suppose you're using Visual Studio. You should configure the Microsoft Visual C++ Redistributable on the client machine. The name of that file is "vcredist_x86.exe". You can find this file on the following location (starting from your Visual Studio folder in Program Files): ...\SDK\v2.0\BootStrapper\Packages\vcredist_x86\vcredist_x86.exe

Unfortunately, this can't be done automatically. From now on, everytime one of my released executable files has to be opened on a machine other than mine, I simply provide "vcredist_x86.exe" in the application folder together with a textfile containing general program information and telling the user to open "vcredist_x86.exe" when they cannot open the executable file the first time. Little time, little effort.

This is just A (not THE) solution to not being able to open executable files on other client machines. There are many other solutions out there, but this one turned out to work just fine for me. Try a search engine if you want to use another solution.

Hope this helps you a bit.

This post has been edited by skater_00: 18 May 2008 - 06:10 PM