March 2004 - Posts

64-bit calling convention and PInvoke bugs
16 March 04 11:28 AM | joshwil | 12 Comments   

Ok, so Word for the Mac is failing me right now. I've tried twice to start this entry there and both times Word has gone kaput on me. Back to my trusty text editor… As for the inevitable "why Mac?" question... Well, I still haven't found a laptop Read More...

Filed under: Writing code targeted at 64bit., Writing agnostic code.

Behavior of 1.0/1.1 managed apps on 64bit machines
13 March 04 01:55 PM | joshwil | 28 Comments   

As I alluded to in my previous post there are multiple ways that we can go in terms of supporting legacy 1.0/1.1 assemblies on a Win64 machine. The context of the 1.0/1.1 support story is made somewhat simpler by the current plan of having both a v2.0 Read More...

Filed under: Writing code targeted at 64bit., Writing agnostic code.

As promised, what is the WOW64 and what does it mean to managed apps that you run on 64bit machines?
11 March 04 04:11 PM | joshwil | 23 Comments   

So, what is the WOW64? If you already have a firm grasp please feel free to skip these first few paragraphs to the section titled “Break in here for the .Net perspective” . When I went and Google’d a bit to see if anyone had a convincing Read More...

Filed under: Writing code targeted at 64bit., 64bit CLR Implementation Goo, Writing agnostic code.

Some good 64bit background info (the next post will be about CLR and WOW64, promise!)
10 March 04 06:39 PM | joshwil | 0 Comments   

I plan to mix things up here a little bit, in that sometimes I'll talk about writing managed code to run on a 64bit box (both in 32bit and 64bit modes), sometimes I'll talk about how the CLR is implemented to make it work well on 64bit boxes, and sometimes Read More...

Filed under: 64bit non-managed rants and raves!

Bigger pointers == More traction!!
10 March 04 12:12 PM | joshwil | 3 Comments   

Start off with a joke... Isn't that what they recommend? This particular joke stems from when Seattle ended up covered in snow this past January and it seemed that for whatever reason the CLR 64bit team were the only people who ended up working in our Read More...