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" <ac************@a-znet.comwrote in message
news:OJ**************@TK2MSFTNGP02.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" <Bi**@NOSPAM.comwrote in message
news:50**********************************@microsof t.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" <ac************@a-znet.comwrote in message
news:eY**************@TK2MSFTNGP05.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.rgvar
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