error when integrating asp.net2.0

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • arun240
    New Member
    • Aug 2008
    • 3

    error when integrating asp.net2.0

    we done the integration in ASP and then they moved to ASP.net both of which was working fine. Initially we had asp.net 1.0 version.
    Now we have moved to 2.0 version and while doing the same they are facing the below error.

    Unable to cast COM object of type 'System.__ComOb ject' to class type 'e24TranPipeLib .e24TranPipeCtl Class'. COM components that enter the CLR and do not support IProvideClassIn fo or that do not have any interop assembly registered will be wrapped in the __ComObject type. Instances of this type cannot be cast to any other class; however they can be cast to interfaces as long as the underlying COM component supports QueryInterface calls for the IID of the interface.
    Last edited by jhardman; Sep 18 '08, 10:02 PM. Reason: Moved to .NET forum. ASP forum is for "classic" ASP only
  • arun240
    New Member
    • Aug 2008
    • 3

    #2
    problem with asp.net2.0 pages when using dll

    we done the integration in ASP and then they moved to ASP.net both of which was working fine. Initially we had asp.net 1.0 version.
    Now we have moved to 2.0 version and while doing the same they are facing the below error.

    Unable to cast COM object of type 'System.__ComOb ject' to class type 'e24TranPipeLib .e24TranPipeCtl Class'. COM components that enter the CLR and do not support IProvideClassIn fo or that do not have any interop assembly registered will be wrapped in the __ComObject type. Instances of this type cannot be cast to any other class; however they can be cast to interfaces as long as the underlying COM component supports QueryInterface calls for the IID of the interface.

    Comment

    • kenobewan
      Recognized Expert Specialist
      • Dec 2006
      • 4871

      #3
      Have you imported the dll?

      Comment

      • Frinavale
        Recognized Expert Expert
        • Oct 2006
        • 9749

        #4
        I think you're going to want to implement Marshalling between the DLL and your .NET code. Look into Marshalling (or Marshaling is the other spelling) for a better understanding of what's going on here.

        Comment

        Working...