Locating the source DLL behind a COM+ ProgId
Bit of background The project is using a COM+ component. These are defined in Classic ASP using the syntax; Set obj = Server.CreateObject("[insert COM+ ProgId]") The this project you are using a component registered with the ProgId CookieOrder.CookieRequest There are many out of the box COM+ components available to Classic...
Failed to generate type library for iAnywhere.Data.SQLAnywhere
c#,entity-framework-5,com+,sqlanywhere,type-library
When I tried to register the assembly through the console. It shows: An unknown exception occurred during installation: 1: System.IO.FileNotFoundException - Could not load file or assembly 'EntityFramework, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. It turns out that after I installed...
BizTalk and COM+
No, not out of the box. You can write a custom Adapter than wraps the COM+ comp and submits messages to you BizTalk app. However, your current plan is more than serviceable so I would stick with that....
Unable to find UIRibbon in Component Service or OleView
how windows manages to find the COM component with corresponding CLSID CoCreateInstance: The CoCreateInstance function provides a convenient shortcut by connecting to the class object associated with the specified CLSID, creating an uninitialized instance, and releasing the class object. As such, it encapsulates the following functionality: CoGetClassObject... CoGetClassObject: A...
Avoid classes to be registered in a COM+ Serviced Component
ComVisibleAttribute is the correct attribute to use. In AssemblyInfo.cs you can use [assembly: ComVisible(false)] so that everything is not COM visible by default, and then for classes which you do want to be visible, precede them with [ComVisible(true)] public class MyClass Or flip it the other way round, if you...
Serviced Component interface not showing up
I figured it out. Turns out i was using a namespace that probably was used in another component. I changed the namespace for my component and it worked