compile .net on vista, can't run on xp

  • Thread starter Thread starter nik
  • Start date Start date
N

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

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
 
Check the versions of the framework on your vista and XP systems.

Mike.
Click to expand...

I've checked the frameworks. The development (vista) machine had 1.0,
1.1, 2.0, and 3.0. The xp machine only had 1.0, 1.1 and 2.0, so I
installed 3.0 and 3.0SP1. Same error. Then just in case I installed
3.5 on the xp machine, and still no luck.

I can understand that this could be an issue, but if I have matching
frameworks on the the two machines and/or a more updated xp machine,
shouldn't it correct such an issue.

Anything else that I am missing?

Thank you
 
nik said:
I've checked the frameworks. The development (vista) machine had 1.0,
1.1, 2.0, and 3.0. The xp machine only had 1.0, 1.1 and 2.0, so I
installed 3.0 and 3.0SP1. Same error. Then just in case I installed
3.5 on the xp machine, and still no luck.

I can understand that this could be an issue, but if I have matching
frameworks on the the two machines and/or a more updated xp machine,
shouldn't it correct such an issue.

Anything else that I am missing?
Click to expand...

The fact that you complied something on Vista, and it was deployed to XP.
It may or may not work, and in this case, it doesn't work. In many cases
when something is compiled on XP and deployed to Vista, it doesn't work as
seen by the many posts in Vista NG(s) about some user installing something
on Vista that works on XP and was meant for XP, but it started blowing-up
other applications on Vista or Vista stopped working.

One should compile the application and deploy it to the platform it is
intended to run on -- XP to XP and Vista to Vista.
 
Mr. Arnold said:
One should compile the application and deploy it to the platform it is
intended to run on -- XP to XP and Vista to Vista.
Click to expand...

There used to be a "rule" stating.... develop and compile on the oldest
platform you plan to support. Things change so drastically these days,
that's not always the best option.

OP... grab a copy of VPC2007 (ms freeware) and install a "virgin" OS. With
that, you can test installations (and anything else) all day long. When
you're done, just shut it down and say "delete changes" (not exact
wording)... that OS'll still be "virgin" the next time you use it for test
purposes.

You can also make copies of these virtual images, so A can have SQL
installed, while B doesn't... C can have the 2.0 framework, D can have
3.5... and so on. VPC is a *wonderful* tool... especially considering its
price. (no USB support though - looks like ya' gotta pay for that - VMWare,
etc)
 
Ken Halter said:
There used to be a "rule" stating.... develop and compile on the oldest
platform you plan to support. Things change so drastically these days,
that's not always the best option.
Click to expand...

I was never taught that. I was taught to compile the solution and deploy it
to the platform it is intended to run on. I have seen too many issues where
something was done on one machine like Win 2K pro as an example, and it hit
out there on corporate user machines that were XP pro, only to watch
applications break due to DLL H-E-L-L issues on same named DLL(s) on both
platforms.

You see it time and time again that someone has installed something that was
compliant to run of XP, but that same solution was not compliant to run on
Vista, and not only did the application not work, but it broke other
applications and/or Vista itself.

Vista is not the same as XP. Vista is different under the hood, although
they are both NT based O/S(s).
 
That exception code means you have a managed execption, nothing more. Most
likely you have an untrapped exception. But, without the exception message or
type, it's hard to know what's happening. What kind of app is this? ASP.NET,
Winforms, something else?
Click to expand...

Its a pretty simple form application. It basically just recurses a
directory structure and does some string parsing on the files it
finds. Since the application can't even start on xp, it would seem
that this exception occurs during the initialization, as opposed to
the code that executes when the user controls the application. The
code seemed like the only relevant part of the windows error report
log, but is there more information there, such as a message or a type?
Is there a way to find the error message or type in this situation?

Thanks,
Nik
 
Hi nik,

nik said:
Its a pretty simple form application. It basically just recurses a
directory structure and does some string parsing on the files it
finds. Since the application can't even start on xp, it would seem
that this exception occurs during the initialization, as opposed to
the code that executes when the user controls the application. The
code seemed like the only relevant part of the windows error report
log, but is there more information there, such as a message or a type?
Is there a way to find the error message or type in this situation?
Click to expand...

Just curious, does the app use the VB MyApplciation stuff ? Is it set to
SingleInstance ? And does the XP computer have a 3rd party firewall ?
 
Hi nik,






Just curious, does the app use the VB MyApplciation stuff ? Is it set to
SingleInstance ? And does the XP computer have a 3rd party firewall ?
Click to expand...

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.
 
Back
Top