Hello from my new PC ... my Xmas present to myself: an AMD 6-core with 8GB of RAM in a "silent" case. I put the parts together on Thursday afternoon and I am attempting to launch the thing and go experimentally live now, at 5pm on Sunday. That's how long it takes to build a new development machine. I was going to smash a bottle of champagne over it, but I needed to drink the bottle instead. This is my first 64-bit OS as a primary development machine and I discovered a few irritating traps for the record:
. I had %ProgramFiles% coded in many dozens of batch files and post-build events, which needed to be smartened to check for %ProgramFiles(x86)% and change behaviour accordingly. . Some COM components did not appear in dcomcnfg, so after a bit of suffering I found you have to use comexp.msc /32 to reveal the 32-bit ones and configure them. . Some Windows Services wouldn't install until I called installutil.exe from the Framework v4.0.30319 folder, whereas I was calling from the v2 folder previously without problems. Most of my time was wasted on getting ASP.NET and Silverlight apps working again. It's just a brain-drain chore to get all of the virtual directories and permissions back to a working state. The rest of the time was spent just getting the hundred or so solutions to compile again due to dependencies on 3rd party libraries like ComponentOne, Visifire, WPF Toolkits, Silverlight toolkits., T4 templates, utility DLLs, etc. These damn things have to be installed and registered, it's the reverse of knocking over dominoes. Greg
