Hi. I am very new to COM+ and am having a bit of trouble. I created a component and registered it, and everything worked fine. Then I made some changes to the interface and needed to recompile the dll. I started the VB application that I reference the dll in and it is not in the References list anymore. Why? Well, not knowing what else to try, I deleted the application from Component Services Manager and then re-registered the whole thing. Even after that, the dll is still not showing in my VB References list. Any ideas on what I'm doing wrong? How can I re-register this component? Any and all help is greatly appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
New to COM+, need help w/registering component
- Thread starter kateyez44
- Start date
SemperFiDownUnda
Instructor
When you change the interface you old programs will have to have their references updated (often you'll look in the list and see one or more references with the description "MISSING"
Just uncheck that and go down in the list until you see your component and select it agian.
I'll explain what is going on here. When you set up a reference in VB it actually doesn't store the name of the library you are using but its Global Unique Identifier (or GUID for short). When you change an interface this GUID changes (if you pick no compatibility or binary compatibility). Binary Compatibility just warns you that you've changed the interface.
This is a safety mechinism so that applications break right away if the appropriate library isn't there instead of getting the user half way into the app before crashing.
Just uncheck that and go down in the list until you see your component and select it agian.I'll explain what is going on here. When you set up a reference in VB it actually doesn't store the name of the library you are using but its Global Unique Identifier (or GUID for short). When you change an interface this GUID changes (if you pick no compatibility or binary compatibility). Binary Compatibility just warns you that you've changed the interface.
This is a safety mechinism so that applications break right away if the appropriate library isn't there instead of getting the user half way into the app before crashing.
- Status