BUG: The Microsoft .NET Framework Assembly Registration Utility Registers the Primary Interop Assembly with the Wrong Version Number Under the Type Library Key (817056)
The information in this article applies to:
- Microsoft .NET Framework 1.1
IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry SYMPTOMSWhile creating a Primary Interop Assembly (PIA), the
Microsoft .NET Framework Assembly Registration utility (RegAsm.exe) registers
the version number of the Type Library in decimal value with "Major.Minor"
format. WORKAROUNDTo work around this bug, follow these steps:
- Use RegAsm.exe with the
/Regfile command line
option.
This generates the .reg file that contains the registry files
that you need. - Manually edit the decimal value of the version number.
Change the value to the corresponding hexadecimal value, and then run the .reg
file.
RegAsm.exe depends on Oleaut32.dll to register the Type Library
and the registry information that it does not write to the .reg file when you
run RegAsm.exe by using the /Regfile option. To correct the
problem, follow these steps:
- Run RegAsm.exe one time without using the
/Regfile option.
- Run RegAsm.exe by using
/Regfile.
- Edit the .reg file.
- Run RegAsm.exe.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are
listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 4/16/2003 |
---|
Keywords: | kbCOMInterop kbbug KB817056 kbAudDeveloper kbAudITPRO |
---|
|