Star Windows x64 Watch List
Linked by David Handlos on Thu 25th Sep 2008 18:07 UTC
Windows A Windows developer and Sysadmin has compiled a "Watch List" of the small but annoyingly important things to keep in mind when moving from 32 bit Windows to Windows x64.
E-mail Print r 3   · Read More · 44 Comment(s) http://osne.ws/foq
Thread beginning with comment 331528
To read all comments associated with this story, please click here.
Some additions
by google_ninja on Thu 25th Sep 2008 20:28 UTC
google_ninja
Member since:
2006-02-05

IIS can run either as a 64-bit or 32-bit process


This is true, however if you are talking about the need to run an ASP.net app in 32-bit, it is alot less drastic to flip the "Enable 32-bit Applications" flag in the app pool advanced settings screen.

Unfortunately, if the application was designed to run as a 32-bit application, it may run into dependency issues when moving up to 64-bit. For example, if the application depended on registry entries, system files, or ODBC settings that were set up for 32-bit applications, the program would likely fail, since it wouldn't be able to access those resources while in 64-bit mode.


One big thing I ran into was that JET interop simply doesn't exist in the 64-bit framework. I have an app that will import Excel files, and for the life of me couldn't figure out why it would work on one machine, but not another. If you need JET interop, go into the project properties in studio, go to the Build tab, and flip Platform Target from "Any CPU" to "x86". This will force the JIT compiler to generate 32-bit native code instead of 64-bit.

Reply Bookmark Score: 2