Thomas Rizzo, Director (!) on the SQL Server Product Management team, kicks off his WinFS column with an overview of why we need it and what it is. I always love the first piece in any column, as it sets the grounding information for what readers are going to need to understand reading future pieces. I especially love them from internal folks, as it really gives a flavor of what the product team (WinFS, in this case), had in mind that drove them to build their thing the way they did. Check it out.
Josh Williams, an SDE on the CLR team, kicks off his 64-bit blog with an introduction to WOW64 and what it means for .NET programmers. Here’s the summary:
WOW64 isn’t the OS per se, but a subset of the Win64 OS which enables a 32bit application to run inside of a 32bit process on a 64bit OS while using 32bit system dlls and such.
Whidbey CLR will include both 32bit and 64bit versions, both of which will be installed on 64bit machines. This allows both 32bit and 64bit managed applications to run in bitness correct native process depending on how the assemblies are tagged at compile time.
Once a process is started up as either 32bit or 64bit all of the dlls/assemblies that are loaded into that process have to be compatible with that bitness.
If you have a 32bit managed app which has dependencies on 32bit unmanaged code then you’ll need to either find a 64bit version of the unmanaged code or tag your managed app as x86 at compile time to make sure that you don’t float up to a native 64bit process. This will result in you having to live with your process running under the WOW64.
