Upgrading from Microsoft Office 2000 Developer

If you are upgrading from an earlier version of Microsoft® Office Developer, the installation process for Office XP Developer will have minimal effect on your existing work. However, there are a few issues you should be aware of to make sure the process goes smoothly.

Office XP Developer installs side-by-side with Office 2000 Developer, so if you do not want to uninstall your earlier version you can continue to use it. However, before you install the workflow components for Microsoft® SQL Server™, you must run an uninstall update procedure and uninstall all Access Workflow Designer components. For more information, see Upgrading from Access Workflow Designer for SQL Server.

The Packaging wizard in Office XP Developer has introduced a number of design changes that improve performance. If you have packages that you created in Office 2000 Developer, however, you will not be able to work with them in the newer version because of these changes. You can continue to work on those packages in Office 2000 Developer if you do not uninstall it, or you can re-create the packages and take advantage of the new features in Office XP Developer.

You can import your existing code libraries into the redesigned Code Librarian. If you have code indexed under multiple categories, you will find that the Code Librarian creates a new copy of the code for each category. If you change the code in one category, the other copies will remain unchanged. This is different from the behavior in Office 2000 Developer, which pointed to the same code from each category.

Other add-ins that are installed with both Office 2000 Developer and Office XP Developer will exist side-by-side if you maintain both versions on your computer. The older add-ins will not be replaced with newer versions.

See Also

Upgrading from Previous Versions | Upgrading from Workflow Designer for Exchange 2000