"The assembly could not be found" error message when loading an Office 2003 managed code extension in Excel 2003 and in Word 2003

When you open a Microsoft Office Word 2003 document or a Microsoft Office Excel 2003 workbook with a managed code extension that was created by using Microsoft Visual Studio Tools for the Microsoft Office System, you may receive the following error message:

This error may occur if the assembly name contains a comma.

Note For additional causes of this error, see the "Troubleshooting in Office at Run Time" topic in the Visual Studio Tools for Office documentation.

To resolve this behavior, change the assembly name so that the assembly name does not contain the comma character.

This behavior is by design.

Steps to reproduce the behavior

1. Start Microsoft Visual Studio .NET 2003.
2. On the File menu, point to New, and then click Project.
   
   The New Project dialog box appears.
3. In the Project Types list, double-click Microsoft Office System Projects, and then click Visual Basic Projects.
4. In the Templates list, select Excel Workbook.
5. In the project Name box, type Comma, Test, and then click OK.
   
   Microsoft Office Project Wizard appears.
6. In Microsoft Office Project Wizard, click Finish.
7. On the Debug menu, click Start to build and to run the solution.
   
   Excel 2003 starts and then opens the workbook. However, you may receive the error message that is mentioned in the "Symptoms" section, and the assembly is not loaded. The error message indicates that the assembly cannot be found.
8. Quit Excel 2003. Return to Visual Studio .NET.
9. To resolve this behavior, follow these steps:
   1. On the Project menu, click Comma, Test Properties.
   2. In the Assembly Name box, type Comma Test, and then click OK.
   3. On the Debug menu, click Start to build and to run the solution.
      
      Excel 2003 starts and then opens the workbook. You do not receive the error message that is mentioned in the "Symptoms" section.