Comments on: The Case of 64-Bit .NET Upgrade Bug

By: Latest Upgrade Auctions : World online computer review

Latest Upgrade Auctions : World online computer review — Thu, 04 Mar 2010 05:22:54 +0000

[...] The Case of 64-Bit .NET Upgrade Bug | Caffeinated Coder [...]

By: uberVU - social comments

uberVU - social comments — Fri, 26 Feb 2010 04:18:03 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by dhelper: Reading: The Case of 64-Bit .NET Upgrade Bug http://bit.ly/b6f9yv...

By: Steve

Steve — Thu, 25 Feb 2010 10:39:15 +0000

Developers should do the required steps (testing on both platforms, checking dependencies) before releasing as AnyCPU, x86 code will work everywhere.

I still think this is the best solution, nobody is stopping you to still release an AnyCPU application but then you can be sure that it will also be tested on x64.

Lots of .NET applications don’t work on x64 windows because they were compiled with AnyCPU, I even have a shortcut to corflags / 32bit to change these applications.

By: The Morning Brew - Chris Alcock » The Morning Brew #547

The Morning Brew - Chris Alcock » The Morning Brew #547 — Thu, 25 Feb 2010 08:35:20 +0000

[...] The Case of 64-Bit .NET Upgrade Bug – Russell Ball shares a useful reminder of some of the problems you can run into when upgrading projects and running them on different processor architectures even in the .NET world. [...]

By: Ben

Ben — Thu, 25 Feb 2010 02:57:28 +0000

Steve,

I am not convinced that x86 as a default is a good thing moving forward. It seems to be a hack to avoid fixing the real problem.

I too have run into the SQL CE issue before. It can be frustrating to resolve until you realize the cause. Until CE has proper 64-bit support, this is the only solution. However, it is only a stop-gap measure and not the ideal fix.

By: Diego Caravana

Diego Caravana — Wed, 24 Feb 2010 16:40:45 +0000

Same problem and same fix with my brand new Win7 64 development laptop, and a WPF app with VLC plugin (which is 32 bit). I must confess that was the first thing a tried, without too much research (lucky strike, I mean).

By: BlackWasp

BlackWasp — Wed, 24 Feb 2010 16:39:37 +0000

I saw a similar issue on a simple application that used an Access database. There’s no 64-bit Jet driver so it all falls over in a heap.

Same solution, force the app to run as 32-bit.

By: Steve

Steve — Wed, 24 Feb 2010 13:07:53 +0000

The good news is that in VS2010 new projects will automatically target x86 instead of AnyCPU.

We had the same problem with SQL CE not installing the x64 redist in a clean .NET 3.5 install.