We have a COM object (vb) that is used in several Clasic ASP and ASP.NET applications. However, the ASP.net applications can no longer locate the COM object when it is re-compiled and re-registered (with a new version number). The Error message is "ClassFactory cannot supply requested class".
I understand that this error is caused because the .Interop.dll has the object's GUID embeded into it and when the re-registration occurs, the GUID is diffrent. What I do not understand is what I can do about it.
I would like to be able to upgrde the COM Object without having to update every .NET Application that uses it.
BChan
Paul Clement - 06 Jul 2004 19:17 GMT
¤ We have a COM object (vb) that is used in several Clasic ASP and ASP.NET applications. However, the ASP.net applications can no longer locate the COM object when it is re-compiled and re-registered (with a new version number). The Error message is "ClassFactory cannot supply requested class".
¤
¤ I understand that this error is caused because the .Interop.dll has the object's GUID embeded into it and when the re-registration occurs, the GUID is diffrent. What I do not understand is what I can do about it.
¤
¤ I would like to be able to upgrde the COM Object without having to update every .NET Application that uses it.
¤
Make certain to compile your COM component using binary compatibility
(Project...Properties...Component tab). This will retain the existing CLSID.
However, if you break binary compatibility by removing interface members, changing arguments, etc.
then you will have to recreate the interop library.
Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)