Com Interop generating wrong cases for interfaces
- From: "Conor Maguire" <TheMig@xxxxxxxxxxxxxxxx>
- Date: Fri, 1 Apr 2005 17:13:50 +0100
Folks,
We have a C# method which we register as part of a class for COM Interop:
public void send(string contents, string filepath ,string filename)
{
}
The type library produced for the assembly contains the following method
information:
void send(
[in] BSTR contents,
[in] BSTR FilePath,
[in] BSTR FileName);
Notice how the original parameters filename and filepath have been changed
to FileName and FilePath.
This is breaking all of our COM bindings in a significant amount of XLANG
schedules as the parameter messages need re-created. We cannot afford to do
this.
Also notice how the parameter signiature has not been changed.
Builds over 2 weeks have been fine through VS.NET, because older DLLS from
our SourceSafe database actually compile for InterOp correctly using
TBLEXP.exe - i.e. the com interfaces get generated with lowercase letters.
Very confused! Can anyone suggest a solution for this, as we now cannot
deploy new codebases to production.
Thanks in advance,
Conor
.
- Follow-Ups:
- RE: Com Interop generating wrong cases for interfaces
- From: "Peter Huang" [MSFT]
- Re: Com Interop generating wrong cases for interfaces
- From: Mattias Sjögren
- RE: Com Interop generating wrong cases for interfaces
- Prev by Date: Re: Professional courtesy and feedback requested
- Next by Date: Re: Professional courtesy and feedback requested
- Previous by thread: Manipulate MSOffice programs from web page or smart client?
- Next by thread: Re: Com Interop generating wrong cases for interfaces
- Index(es):
Relevant Pages
|