could not convert the signature for member DISPPARAMS.rgvar

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Academia
    #1

    could not convert the signature for member DISPPARAMS.rgvar

    in vs2005 I added a reference to component name "tom" from riched20.dll.

    In vs2008 I now get the warning:
    Type library importer could not convert the signature for member
    DISPPARAMS.rgva r

    The rich edit controls that ships with XP SP1 is in Msftedit.dll (v4.1) and
    Riched20.dll (v3.0)

    I don't see Msftedit.dll as one of the options for selecting a COM reference
    to the project.
    1)Why isn't it included in the list?? How is that list built?

    I Suppose the .NET richtextbox is built on Riched20.dll
    2)Is that correct?? Is there some way I can check?

    3)How can I get rid of the warning.

    4) Is the fact that importer can't convert it apt to cause me problems?


    Thanks for any answers


    Tags: None
    • Bill McCarthy
      #2
      Re: could not convert the signature for member DISPPARAMS.rgva r

      Hi Academia,

      Grab the source code for the VB Snippet Editor as it has a tom
      implementation:

      Home
      http://billmccarthy.com/Projects/Snippet_Editor/default.html




      "Academia" <academiaNOSPAM @a-znet.comwrote in message
      news:eY5aTqWXIH A.1212@TK2MSFTN GP05.phx.gbl...
      in vs2005 I added a reference to component name "tom" from riched20.dll.
      >
      In vs2008 I now get the warning:
      Type library importer could not convert the signature for member
      DISPPARAMS.rgva r
      >
      The rich edit controls that ships with XP SP1 is in Msftedit.dll (v4.1)
      and Riched20.dll (v3.0)
      >
      I don't see Msftedit.dll as one of the options for selecting a COM
      reference to the project.
      1)Why isn't it included in the list?? How is that list built?
      >
      I Suppose the .NET richtextbox is built on Riched20.dll
      2)Is that correct?? Is there some way I can check?
      >
      3)How can I get rid of the warning.
      >
      4) Is the fact that importer can't convert it apt to cause me problems?
      >
      >
      Thanks for any answers
      >
      >

        Comment

        • Academia
          #3
          Re: could not convert the signature for member DISPPARAMS.rgva r

          I will, but can you tell me what is going on?
          Is this tom implementation something you fixed?
          If not, where did it come from?


          Thanks a lot

          "Bill McCarthy" <Bill@NOSPAM.co mwrote in message
          news:50A8AD6F-2D6E-459A-9C49-04A1963AFBB7@mi crosoft.com...
          Hi Academia,
          >
          Grab the source code for the VB Snippet Editor as it has a tom
          implementation:
          >
          Home
          http://billmccarthy.com/Projects/Snippet_Editor/default.html

          >
          >
          >
          "Academia" <academiaNOSPAM @a-znet.comwrote in message
          news:eY5aTqWXIH A.1212@TK2MSFTN GP05.phx.gbl...
          >in vs2005 I added a reference to component name "tom" from riched20.dll.
          >>
          >In vs2008 I now get the warning:
          >Type library importer could not convert the signature for member
          >DISPPARAMS.rgv ar
          >>
          >The rich edit controls that ships with XP SP1 is in Msftedit.dll (v4.1)
          >and Riched20.dll (v3.0)
          >>
          >I don't see Msftedit.dll as one of the options for selecting a COM
          >reference to the project.
          >1)Why isn't it included in the list?? How is that list built?
          >>
          >I Suppose the .NET richtextbox is built on Riched20.dll
          >2)Is that correct?? Is there some way I can check?
          >>
          >3)How can I get rid of the warning.
          >>
          >4) Is the fact that importer can't convert it apt to cause me problems?
          >>
          >>
          >Thanks for any answers
          >>
          >>
          >

            Comment

            • Bill McCarthy
              #4
              Re: could not convert the signature for member DISPPARAMS.rgva r

              Hi,

              All the relevant code is inside the CodeEditor.vb file. The relevant COM
              interfaces and some helper native methods are in there to get the
              interfaces. These are equivalent of managed interface declarations for the
              tom, so you don't need to reference the tom.


              "Academia" <academiaNOSPAM @a-znet.comwrote in message
              news:OJSmylcXIH A.5396@TK2MSFTN GP02.phx.gbl...
              >I will, but can you tell me what is going on?
              Is this tom implementation something you fixed?
              If not, where did it come from?
              >
              >
              Thanks a lot
              >
              "Bill McCarthy" <Bill@NOSPAM.co mwrote in message
              news:50A8AD6F-2D6E-459A-9C49-04A1963AFBB7@mi crosoft.com...
              >Hi Academia,
              >>
              >Grab the source code for the VB Snippet Editor as it has a tom
              >implementation :
              >>
              >http://billmccarthy.com/Projects/Sni...r/default.html
              >>
              >>
              >>
              >"Academia" <academiaNOSPAM @a-znet.comwrote in message
              >news:eY5aTqWXI HA.1212@TK2MSFT NGP05.phx.gbl.. .
              >>in vs2005 I added a reference to component name "tom" from riched20.dll.
              >>>
              >>In vs2008 I now get the warning:
              >>Type library importer could not convert the signature for member
              >>DISPPARAMS.rg var
              >>>
              >>The rich edit controls that ships with XP SP1 is in Msftedit.dll (v4.1)
              >>and Riched20.dll (v3.0)
              >>>
              >>I don't see Msftedit.dll as one of the options for selecting a COM
              >>reference to the project.
              >>1)Why isn't it included in the list?? How is that list built?
              >>>
              >>I Suppose the .NET richtextbox is built on Riched20.dll
              >>2)Is that correct?? Is there some way I can check?
              >>>
              >>3)How can I get rid of the warning.
              >>>
              >>4) Is the fact that importer can't convert it apt to cause me problems?
              >>>
              >>>
              >>Thanks for any answers
              >>>
              >>>
              >>
              >
              >

                Comment

                Previous template Next
                Working...