On Monday, 15 April 2002 17:19:04 UTC+5:30, Geir Stian Aaslund wrote:
The problem with this may be that you have different id's for the same put/get
This code is wrong:
[id(0x60030017), propput]
HRESULT ActiveQuestion([in] short );
[id(0x60030018), propget]
HRESULT ActiveQuestion([out, retval] short* );
replace it with
[id(0x60030017), propput]
HRESULT ActiveQuestion([in] short );
[id(0x60030017), propget]
HRESULT ActiveQuestion([out, retval] short* );
Geir Stian
declangoodman@yahoo.com (Deco) wrote in message news:<b3b50459.0203250330.4a3a31dd@posting.google.com>...
Hi there,
I am trying to compile an IDL file (named XMLProjectLoader.idl), and
get the following MIDL output:
Microsoft (R) 32b/64b MIDL Compiler Version 6.00.0347
Copyright (c) Microsoft Corp 1991-2000. All rights reserved.
Processing .\XMLProjectLoader.idl
XMLProjectLoader.idl
Processing c:\microsoftSDK\Include\oaidl.idl
oaidl.idl
Processing c:\microsoftSDK\Include\objidl.idl
objidl.idl
Processing c:\microsoftSDK\Include\unknwn.idl
unknwn.idl
Processing c:\microsoftSDK\Include\wtypes.idl
wtypes.idl
Processing c:\microsoftSDK\Include\basetsd.h
basetsd.h
Processing c:\microsoftSDK\Include\guiddef.h
guiddef.h
Processing c:\microsoftSDK\Include\oaidl.acf
oaidl.acf
midl\oleaut32.dll : error MIDL2020 : error generating type library : SetFuncAndP
aramNames failed : get_serialVersionUID (0x8002802C)
The only documentation I can find relating to this error is:
One cause of this error is if the path to the .IDL file is longer than
126 characters, which is because oleaut32.dll does not currently
support path names that are greater than 126 characters. The
workaround is to reduce the path to the .IDL file so that it is less
than 126 characters.
Does the 'path' length include the length of the methods exposed in
the IDL file? My idl methods are long, but nothing near 126 chars.
Does anyone know what else could cause this IDL error?
Thanks in advance.
Deco
Thanks,
It is working.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)