Issue with running .exe(compiled in 34 bit) in window7 64bit enviornment
-
I m having a visualstudio 2008 project all debug folder files. The exe runs well in winxp and window7 32 bit but problem arises when i try to run in window7 64 bit. Plz help me how to resolve this issue. Any comments are welcome
-
I m having a visualstudio 2008 project all debug folder files. The exe runs well in winxp and window7 32 bit but problem arises when i try to run in window7 64 bit. Plz help me how to resolve this issue. Any comments are welcome
I can understand you get problems when you compile the exe for 34 bits... But seriously: You need to post more about the error you're getting. It could be an issue with loading 3rd part assemblies, but it's impossible to say when you don't post any error information.
-
I can understand you get problems when you compile the exe for 34 bits... But seriously: You need to post more about the error you're getting. It could be an issue with loading 3rd part assemblies, but it's impossible to say when you don't post any error information.
when exe is run in window7 64 bit then gets error msg i-e Unhandled exception has occured in your application . If u click continue the application will ignore this error and attempt to continue.if u click quit the application will close immediatly. Input string was not in correct format.
-
when exe is run in window7 64 bit then gets error msg i-e Unhandled exception has occured in your application . If u click continue the application will ignore this error and attempt to continue.if u click quit the application will close immediatly. Input string was not in correct format.
-
No. if you dont mind then Can u plz provide me ur email so that i could send u exe and u would better able to find issue.
-
No. if you dont mind then Can u plz provide me ur email so that i could send u exe and u would better able to find issue.
-
I'll happily do your work for you, if you'll agree to my daily rate. Minimum 1 day @ £475/day.
:( which is not even my one month pay
-
:( which is not even my one month pay
In which case, why dont you do one or more of the following: 1) Improve error handling in your app so you can catch the exact error message. Post this to allow people to help you in the way forums are meant to be used. 2) Google for the no-doubt common problem of 32bit .net apps failing unexpectidly on 64bit OS's 3) Step through your code on a copy of a 64bit OS to see if you can debug the problem in the traditional way. My response above was not a serious solicit for work, it was to point out to you that most of the people who answer questions here are professional programmers (which you may or may not be), but we generally don't give away our services for free. We are however, usually happy to assis where the questioner has put in the minimum level of effort to solve their own problem.
-
In which case, why dont you do one or more of the following: 1) Improve error handling in your app so you can catch the exact error message. Post this to allow people to help you in the way forums are meant to be used. 2) Google for the no-doubt common problem of 32bit .net apps failing unexpectidly on 64bit OS's 3) Step through your code on a copy of a 64bit OS to see if you can debug the problem in the traditional way. My response above was not a serious solicit for work, it was to point out to you that most of the people who answer questions here are professional programmers (which you may or may not be), but we generally don't give away our services for free. We are however, usually happy to assis where the questioner has put in the minimum level of effort to solve their own problem.
thankz. Actually client have just exe file not sourcecode and asked me to sortout this issue. some one suggested me corflags .NET utility so i m going to look over it.
-
No. if you dont mind then Can u plz provide me ur email so that i could send u exe and u would better able to find issue.
-
thankz. Actually client have just exe file not sourcecode and asked me to sortout this issue. some one suggested me corflags .NET utility so i m going to look over it.
-
thankz. Actually client have just exe file not sourcecode and asked me to sortout this issue. some one suggested me corflags .NET utility so i m going to look over it.
Typically, this is caused by an application being compiled to target "Any CPU". This means that the code will run as a 32-bit app on 32-bit Windows and as a 64-bit app on 64-bit Windows. The problem comes in when the app uses 32-bit only components and .DLL's. You cannot mix 32 and 64-bit code in the same process, so an app that works fine as 32-bit will fall on it's face when run as 64-bit using the exact same components. The solution is to recompile the app to target x86 only, but you need the source code for that. The other fix is to run it on 32-bit Windows only, be it in a virtual machine or rebuilding the customers machine to run 32-bit Windows instead, but customers tend to frown upon this.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009... -
when exe is run in window7 64 bit then gets error msg i-e Unhandled exception has occured in your application . If u click continue the application will ignore this error and attempt to continue.if u click quit the application will close immediatly. Input string was not in correct format.
HI, What information is seen when the details button on the Unhandled exception dialog is clicked. The exception type and a stack trace should be available even if the application was built in release mode with debug information set to none. Ask your clients to 1) highlight the detailed information by dragging over it with the mouse 2) Press Ctrl-C to copy the highlighted text to the clipboard 3) Paste into Notepad 4) Send you the file. Alan.
-
No. if you dont mind then Can u plz provide me ur email so that i could send u exe and u would better able to find issue.
-
Typically, this is caused by an application being compiled to target "Any CPU". This means that the code will run as a 32-bit app on 32-bit Windows and as a 64-bit app on 64-bit Windows. The problem comes in when the app uses 32-bit only components and .DLL's. You cannot mix 32 and 64-bit code in the same process, so an app that works fine as 32-bit will fall on it's face when run as 64-bit using the exact same components. The solution is to recompile the app to target x86 only, but you need the source code for that. The other fix is to run it on 32-bit Windows only, be it in a virtual machine or rebuilding the customers machine to run 32-bit Windows instead, but customers tend to frown upon this.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009...