Executable runs for one user and not another?
I wrote an application in VB (Visual Studio 2005) and took it to a client's office on a CD. I copied the program.exe to one of the client's computers (running Windows XP) and the program runs fine. I copied it to the computer at the next desk (running Windows 2000), and it aborts immediately with an unhandled exception error. It won't run on their server either (Small Bus Server 2000).
I'm an old VB6 programmer. Did I miss something in the documentation about how to distribute my applications? Is there something wrong with the client not using XP for his operating system?
[595 byte] By [
menacher] at [2007-12-25]
Without seeing the exception its difficult to determine an exact cause BUT
for a VB 2005 application to work requires both version 2.0 of the .net framework to be installed on the machine along with the executable.
It may happen that the first machine had this on already and the second machine didnt. Hence the second machine generated an exception. For deployment I would recomend creating a deployment solution which you can set to include .net 2.0 as a requirement and this will install the framework and any required dll's for you application as part of the installation process rather than simply copying a exe from onto a machine.
No .NET framework on machine, no VB 2005 application wil run.
Windows 2000 is a supported OS for the .NET 2.0 framework but you may need to verify that it is sufficiently patched to a certain Service pack level.
Verify that the 2000 machine has the framework and be more specific about the exception that has occured, what type of application you are trying to run (console, windows, service, web etc.)
