#MAC OFFICE VERSION HISTORY MAC OS#
#MAC OFFICE VERSION HISTORY PRO#
#MAC OFFICE VERSION HISTORY CODE#

Also, CodeWarrior’s parser was picky in different ways from MSVC, so yes, we had scads of errors and warnings to slog through then, too. Interestingly enough, we’ve converted now many of them back to cmd-line (Perl and Python where we could C/C++ still for others) to use with Xcode.

Each custom tool had to be converted from a cmd-line tool to a CodeWarrior plugin.

#MAC OFFICE VERSION HISTORY MAC OS#

All of these had to be redone to work on the Classic Mac OS without a command line. I do recall the conversion taking several months (perhaps 6 all together?) That transition had its own set of headaches, just like our current move to Xcode.įor example, while MSVC only ran on the PC, it could be command-line driven and we had a whole set of scripts, makefiles, custom tools, and other goodies that we used to build Office. I didn’t actually do much of the conversion work either, being fully involved in making Mac Excel 2001 use Unicode internally.

#MAC OFFICE VERSION HISTORY PRO#

Some MacBU folks began to investigate switching over to CodeWarrior (version Pro 5, or so, i think.) Since I was rather new still, having been at Microsoft for less than two years at that point, I was not involved in the planning or decision-making for that switch.

We were the MacBU, for Pete’s sake! Why were we working on PCs?.

Our system required static IPs for our Macs, which ate up corporate network resources unnecessarily.

Dev productivity was not optimal due to waiting for files to be copied over the network every time.

The MSVC compiler had a customized set of Apple OS headers, making it very hard to roll out new headers for new Apple technologies (such as the rapidly evolving QuickTime).

We knew there were some major limitations to our current dev setup: Well, we managed to ship Mac Office 98 and 98-J, and then turned our attention to what eventually became Mac Office 2001. The process worked reasonably well but could be horrifically slow, especially if you were trying to view a large memory window.

#MAC OFFICE VERSION HISTORY CODE#

So, we edited and wrote our code on the PC, compiled it on the PC, and then pushed it over the network to our Macs and debugged it remotely. (Remember how I said that we inherited code that was deemed acceptable to a compiler that wasn’t incredibly standards-compliant at the time?) MSVC4 had a PowerPC cross-compiler (it was used for the PowerPC version of Windows NT) that ran on PCs. The ‘interesting’ part of that project is that we developed Mac Office 98 using the same tools that the Win Office team used - Microsoft Visual C++ version 4.0.

When we sprung forth, we took a copy of the integrated Win+Mac Office source code with us, and that source became Mac Office 98. The debacle known as Mac Word 6 was one of the reasons the MacBU was formed. Prior to the formation of the MacBU, the Win Office team really was the entire ‘Office’ team for both Mac and Win products. (I had actually been an intern the summer before, when the product was optimistically called Office 96 internally!) I worked on Win Excel for a few months, and then joined the MacBU when it was formed. I joined Microsoft in September 1996, right before Win Office 97 shipped.

Now that I stop to recall, that is an interesting topic. Pip asked about my experiences with Mac Office’s previous compiler transitions.

Mac office version history