Creating x64 compatible builds from Visual Studio

Hi

I am developing a Visual Basic application using Visual Studio 2008 / .NET 3.5 on a Win7 x32 machine.

I am experiencing that my application is crashing on x64 installations (win7/8/8.1). I have searched for a solution on how to create an x64 compatible version and I do find a lot of info about this, but it is also quite confusing. Most info I see is related to C# that I am not using.

I do want to avoid a split solution where I must deliver two separate (x32 and x64) versions of my application, because my users would not always be able to make the correct decision on what to use.

Can someone guide me in setting up a simple, yet reliable solution to this problem?
daghoffAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Éric MoreauSenior .Net ConsultantCommented:
why not simply distribute the x86 on the 64-bits platform? Easy and efficient enough for most applications.

and why is your application crashing? any error messages? sometimes it is related to drivers (like odbc, Excel, ...) that are not the same or folders that are different between platforms.
0
it_saigeDeveloperCommented:
Have you tried to determine why it crashes on a 64-bit system?  32-bit builds are compatible with 64-bit operating systems.  So it is possible that a dependency that your application has may have a 64-bit/32-bit version.  More specifically what is the error you are getting when it crashes?

-saige-
0
daghoffAuthor Commented:
Thanks for your feedback. I know I should have supplied more specific info. The last hours I have reinstalled a fresh Win7 x64, installed my program and run it.

The crash does not always show up, but if it does it is usually when I close it. The error message I get is simply that “the program has stopped working”. It offers me the options to close it or search the internet for a solution.

Usually, but not always, I then get a message saying that Windows detected that this program did not run correctly and that compatibility settings has been applied to the program.

And that solves the problem. But I am not happy with this because I would like to prevent the problem from ever occurring in the first place.

I do suspect the crash may have something to do with the program calling Excel and PDFSharp, but I can’t be sure. The problem only shows up when I run on an x64 PC I haven’t used before.

Please see the attachments for problem details.
Any ideas?
Exception1.txt
Exception2.txt
0
Introduction to Web Design

Develop a strong foundation and understanding of web design by learning HTML, CSS, and additional tools to help you develop your own website.

käµfm³d 👽Commented:
You shouldn't have to compile for a specific architecture unless your application has a reliance on a library that was compiled for a specific architecture (e.g. Oracle's ODP.NET). You should be able to compile as "Any CPU" and have the code run in both places if you're not using any such libraries.

Are you logging errors in your application? Logging would (theoretically) give you more insight into what the problem might be.
0
daghoffAuthor Commented:
Can you please specify what you mean by logging and how I apply it. I am running my Visual Studio debugs quite standard I believe.

My gut feeling tells me that there is something that the code has been using while the program was running that can’t be released properly when I close the program. It then ends in a hang/crash state and Windows pops up and applies compatibility mode on the program and the problem does not reoccur.

I have pointed to the use of Excel/PDFSharp as the source of the problem, but it is a fact that using these features gives no problems at all. It is only when I close the program the problems show up.
0
Éric MoreauSenior .Net ConsultantCommented:
I wrote an article on tracing applications a long time ago: http://emoreau.com/Entries/Articles/2003/11/Code-diagnostic-an-article-on-tracing-and-debugging.aspx

Also, are you deploying your application in Debug or in Release mode? I would deploy it after a Debug mode compilation and with the PDB. You might get a little bit more precise exception.

I would also add try...catch to all/most methods called in the application closing to try to find where the exception comes from.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CodeCruiserCommented:
To save you from having to reinstall windows every time you want to reproduce the issue, I think you can turn off compatibility settings by right clicking exe, clicking on properties, going to Compatibility tab and unticking all the tickboxes.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.