.exe compiled on vista doesn't run on xp??

[nik]

Hi,

I've compiled my application on my vista machine, and it won't run at
all on my xp machine. In the windows error report I get Exception
code; 0xe0434f4d. I searched for that exception, but didn't see
anything related to my problem. I can run a different .exe that I made
on the vista machine on the xp machine, so I am wondering what is
different/wrong with this one.

The xp machine does have vb6 installed on it, could that be an issue?
What reasons and solutions for this problem?

Thanks in advance,
Nik

 

[Brian Gideon]

Hi,

I've compiled my application on my vista machine, and it won't run at
all on my xp machine. In the windows error report I get Exception
code; 0xe0434f4d. I searched for that exception, but didn't see
anything related to my problem. I can run a different .exe that I made
on the vista machine on the xp machine, so I am wondering what is
different/wrong with this one.

The xp machine does have vb6 installed on it, could that be an issue?
What reasons and solutions for this problem?

Thanks in advance,
Nik

So we know that at least one executable compiled on the Vista machine
works on XP right? That tells me that the .NET Framework is
*probably* installed correctly on the XP machine. Is the problem
executable using any unmanaged code? That might be part of the
problem. Can you be more specific about the error you're getting?
What makes you think 0xe0434f4d is an error code? It looks like it
coulde be a memory address as well.

 

[Family Tree Mike]

It could be almost anything at this point, except for the vb6 being on the
machine. You should debug on the machine, or at least some machine with XP
on it. Never assume that builds done on XP will run on Vista, or vise
versa. Debugging on the machine should show you where the app is crashing.

 

[Bill McCarthy]

Hi Nik,

Ensure they have the same version of the framework on their machine. Also
you should get VPC (free from Microsoft) and run XP in it to test your apps
before deployment.

 

[nik]

So we know that at least one executable compiled on the Vista machine
works on XP right? That tells me that the .NET Framework is
*probably* installed correctly on the XP machine. Is the problem
executable using any unmanaged code? That might be part of the
problem. Can you be more specific about the error you're getting?
What makes you think 0xe0434f4d is an error code? It looks like it
coulde be a memory address as well.

I don't think I am using unmanaged code, but how do I check for sure?
Is there a compiler setting that would flag unmanaged code?

 

[Mr. Arnold]

I don't think I am using unmanaged code, but how do I check for sure?
Is there a compiler setting that would flag unmanaged code?

Any language that doesn't use the .Net Framework, in particular, the CLI and
CLR is unmanaged code. VB6 is unmanaged code. An example of that would be a
VB.Net solution making a call to COM DLL written in VB6. The COM DLL didn't
originate itself by being complied using a .NET compiler.

 

[nik]

Any language that doesn't use the .Net Framework, in particular, the CLI and
CLR is unmanaged code. VB6 is unmanaged code. An example of that would be a
VB.Net solution making a call to COM DLL written in VB6. The COM DLL didn't
originate itself by being complied using a .NET compiler.

If I understand this correctly, if all of the References under the
solutions properties page are of type .NET and pointing into the .NET
framework, then everything is composed of .NET parts and is therefore
managed code. ie. the solution doesn't reference any unmanaged dll, so
there is no unmanaged code involved.

 

[Michel Posseth [MCP]]

The xp machine does have vb6 installed on it, could that be an issue?

No not if you installed first VB6 and then VS.Net

Well actually 0xe0434f4d. is a basic exception

What reasons and solutions for this problem?

As you do not provide anny detailed info about your application it is hard
guessing what exactly is the problem
but a wild guess from my side is that you use a managed reference that is
not availlable on the target system
maybe you installed a certain SDK on the development system ?

for instance if you use anything from the windows live id classes this will
work on Vista but not on a XP machine without windows Live installed
it will bomb with a 0xe0434f4d exception


regards

Michel Posseth

 

[Michel Posseth [MCP]]

If I understand this correctly, if all of the References under the
solutions properties page are of type .NET and pointing into the .NET
framework, then everything is composed of .NET parts and is therefore
managed code. ie. the solution doesn't reference any unmanaged dll, so
there is no unmanaged code involved.

Just to confirm,, Yes you understand this correctly
But as you wil read in my below post the described error is actually a basic
framework error

;-)

Regards

Michel

 

[nik]

"nik" <[email protected]> schreef in bericht




Just to confirm,, Yes you understand this correctly
But as you wil read in my below post the described error is actually a basic
framework error

;-)

Regards

Michel

fixed by:

Installed .net onto xp machine,
opened solution, it said there was an error in .resx file
deleted the reference to the main forms icon in the .resx file
problem solved

thanks for everyones help.

 

[Brian Gideon]

fixed by:

Installed .net onto xp machine,
opened solution, it said there was an error in .resx file
deleted the reference to the  main forms icon in the .resx file
problem solved

thanks for everyones help.

That's messed up. You'd think the error message would be a little
more descriptive or maybe the runtime would be a little more tolerant
of that situation.

 

[Michel Posseth [MCP]]

Well i still believe that it has to do with something that was availlable on
the Vista system but isn`t availlable on the XP system
as the described error is the most basic framework error there is o.i.o.w.
"every managed error that is thrown up and up in the error mechanism ends
mostly with this error "

for the oldy`s
0xe0434f4d = COM`s runtime error 91 "Object variable or with block not
set" ;-)

the really funny part is
In ASCII, 43 4F 4D translates to "COM". So, E0434F4D was chosen as the
error for for "Exception from a COM object"

So in reall world this error is mostly thrown when you access a object that
is not availlable at runtime


HTH

Michel



"Brian Gideon" <[email protected]> schreef in bericht

fixed by:

Installed .net onto xp machine,
opened solution, it said there was an error in .resx file
deleted the reference to the main forms icon in the .resx file
problem solved

thanks for everyones help.

That's messed up. You'd think the error message would be a little
more descriptive or maybe the runtime would be a little more tolerant
of that situation.