Difference in the compiling modes - COM Discussion Boards

18-Aug-05 11:31

I am trying to get an array created in a COM Server and passed back to the client by the mechanism: [out, size_is(,*pNum_ROI_nodes)] float **pROI_coords

from the .idl file.

Where the pNum_ROI_nodes is the size of the array and pROI_coords is the name of the array.

Problem: I am receiving only one value back in this array on the client side. I have verified that only one value is being allocated in the array by the marshaller in the client side. All data is being loaded into the server side of this array (where it is being created by (float*) CoTaskMemAlloc((resultNodes * 2) * sizeof(float))) The data on the client side is the very first value loaded into it by the server and nothing else except 0x0d f0 ad ba in the second location. (bad food)

Is there some setting for the COM that is confusing the marshaller? The above [out, size_is(,*pNum_ROI_nodes)] float **pROI_coords is only in the *.idl file. Should it be somewhere else as well??

The marshaller just doesn't seem to be getting the idea that there is an array, rather a single value.

Thanks in advance,
David

Vi218-Aug-05 19:54

Vi2

18-Aug-05 19:54

The standard TypeLib marshaller knows nothing about [size_is] keyword for parameter and cannot be used here. Instead you should build the Proxy/Stub DLL and use it to marshal this interface.

With best wishes,
Vita

David_Leikis19-Aug-05 3:26

19-Aug-05 3:26

Thank you for your posting, but I need some more info on how to do what you suggested. Could you tell me some steps on how to do this and how is it different than what I have already done? I don't know the difference.

Regards,
David

Vi219-Aug-05 4:17

Vi2

19-Aug-05 4:17

Look at main cpp file. Here you can find the useful information. Something like that:

// XXXX.cpp : Implementation of WinMain or DLL Exports.

// Note: Proxy/Stub Information
// To build a separate proxy/stub DLL,
// run nmake -f XXXXps.mk in the project directory.

With best wishes,
Vita

David_Leikis19-Aug-05 4:42

19-Aug-05 4:42

I tried to do that from a command prompt window, but got an error:

fatal error C1189: You need a Windows2000 or later to run this stub because it uses the following features: NMAKE: error U1077: 'cl' return code '0x2'. Stop.

Any ideas?

David

Vi222-Aug-05 21:59

Vi2

22-Aug-05 21:59

I don't know what should you do in this case. I didn't use the command prompt window.

1. You can create (and add to existing DSW) the new project which will produce the Proxy DLL. The type of this project is "Makefile" selected from all available projects.

2a. You can add the xxxps.mk file into "Source" files of your project and specify the "Custom Build" for this entry.

2b. You can specify the "Custom Build" (or "Post-biuld step") for your project entry to make and register the Proxy DLL.

IOW, let the VC IDE to run NMAKE into correct environment formed by IDE.

With best wishes,
Vita

RikaBoy26-Aug-05 21:45

RikaBoy

26-Aug-05 21:45

Hi Vita,

I can see you are good with COM and C#. I am new to use c# and I did not use COM before. I would appreciate if you could help me.
I need to execute Cache methods from c# programm. Now Cache does not have yet any interface to c#, but there is COM for c++ 6.
Using this COM in c# I can open Cache DB, but I cannot (I do not know how) to access properties of the classes stored in Cache database.
I exported Cache classes in ODL format. Cache created this file that has uuid and id for every method I created in Cache. Now, my problem is how can I call these methods in C#? I would appreciate if you could refere where can I find any code how to call methods when I have them in odl file.

Thanks in advance,

RikaBoy

-- modified at 3:46 Saturday 27th August, 2005

[Message Deleted]

RikaBoy26-Aug-05 21:18

RikaBoy

26-Aug-05 21:18

[Message Deleted]

Lim Bio Liong19-Aug-05 3:12

19-Aug-05 3:12

Hello David,

I assume that you have declared your array-returning method similar to the following :

[helpstring("method GetFloatArray01")] HRESULT GetFloatArray01([out] LONG* pNum_ROI_nodes, [out, size_is(,*pNum_ROI_nodes)] FLOAT** pROI_coords);

Now, in your code for the server which implements this method, did you assign a proper value for "pNum_ROI_nodes" ?

I created a sample implementation as follows :

STDMETHOD(GetFloatArray01)
(long * pNum_ROI_nodes, float * * pROI_coords)
{
long resultNodes = 5;

*pNum_ROI_nodes = resultNodes * 2; // <-- important.

*pROI_coords = (float*)CoTaskMemAlloc((resultNodes * 2) * sizeof(float));

(*pROI_coords)[0] = 1.0;
(*pROI_coords)[1] = 2.0;
(*pROI_coords)[2] = 3.0;
(*pROI_coords)[3] = 4.0;
(*pROI_coords)[4] = 5.0;
(*pROI_coords)[5] = 6.0;
(*pROI_coords)[6] = 7.0;
(*pROI_coords)[7] = 8.0;
(*pROI_coords)[8] = 9.0;
(*pROI_coords)[9] = 10.0;

return S_OK;
}

Best of luck,
Bio.

David_Leikis19-Aug-05 3:38

19-Aug-05 3:38

Yes, my code is very similar to your example.
1. I have verified that the value for pNum_ROI_nodes is positive and the correct value for the situation.

2. I have seen that all of the values do get loaded into the memory assigned for the array on the server side in the server's memory space.

3. Upon return to the client side, I can see that the value returned for the pNum_ROI_nodes is still the correct value and is in the client memory space, but upon trying to read the values with:

for (int i = 0; i < pNum_ROI_nodes * 2; i++)
{
pfCoordValue[i] = (float)pROI_coords[i]; //retrieve the values to local array
}
CoTaskMemFree(pROI_coords); //delete the array created within the COM server object

At this point, the only value that is in the array pROI_coords, is the very first value loaded. In your example, it would be the value of 1.0. All other values are none existent and it is clear from the memory contents that the array is not initialized past one value. It appears that the marshaller is only moving one item of the array to the client side.

Vita has suggested that the marshaller does not understand the size_is command, maybe he is on to something...

Regards,
David

Lim Bio Liong19-Aug-05 4:04

19-Aug-05 4:04

Hello David,

Just curious about one thing, in your "for" loop :

for (int i = 0; i < pNum_ROI_nodes * 2; i++)
{
pfCoordValue[i] = (float)pROI_coords[i]; //retrieve the values to local array
}

why do you loop until "pNum_ROI_nodes * 2" ?

The returned "pROI_coords" should contain only "pNum_ROI_nodes" number of values right ?

Regards,
Bio.

David_Leikis19-Aug-05 4:13

19-Aug-05 4:13

The array contains the x and y coordinates of each of the nodes that have been found and therefore is two times the number of nodes. They are just packed in sequential pairs.

BTW, this method that I am trying to get going is from a text "Com+ Programming" by Pradeep Tapadiya. It just seems as though this might work if I have the proper settings??? I have seen it on MSDN and other postings as well.

Do you understand what Vita was talking about with a Proxy/Stub DLL and why wouldn't the TypeLib marshaller understand the size_is ?

Thanks,

David

Lim Bio Liong19-Aug-05 4:44

19-Aug-05 4:44

Hello David,

>> The array contains the x and y coordinates of each of the nodes that have been found and therefore is two times the number of nodes. They are just packed in sequential pairs.

I see. However, would I be right in asserting the following :

1. The array is one dimensional nevertheless, as far as COM is concerned.
2. The fact that you have packed pairs of values in the array is a high-level design point.

If I'm correct about the above two points, then take note that "pNum_ROI_nodes" needs to be set to the actual number of elements in the array (which, from a high-level standpoint, would be "two times the number of nodes"). It should not return the "total number of nodes divided by two" - this is a high-level design issue and will not be understood by COM.

The "for" loop in your client code may need to be modified in view of the fact that the logic behind the value of "pNum_ROI_nodes" is now different.

>> Do you understand what Vita was talking about with a Proxy/Stub DLL and why wouldn't the TypeLib marshaller understand the size_is ?

Yes, David. Due to the fact that you are using a non-OLE-automation-compatible array (OLE-automation-compatible arrays would require the use of SAFEARRAYs, the size_is attribute is not relevant here), a Proxy/Stub DLL is required so that the marshaller knows how to properly handle your method and your array (between the server and the client).

The TypeLib marshaller is used when your interface is based on IDispatch and all parameters are based on automation-compatible types.

If you are using VC++ 7.0 (i.e. from Visual Studio .NET), a proxy/stub DLL project is generated automatically for you by the wizard, but you would need to make sure you fully build it. Once it is built, the wizard will register it. Once it is registered, the marshaller will know where to locate it and use it during client run time.

If you are using VC++ 6.0, you would need to build the proxy/stub project and dll manually.

Best Regards,
Bio.

David_Leikis19-Aug-05 5:01

19-Aug-05 5:01

Thanks for your answers Bio.

I am using VC++6.0 so I have to build it manually. I have tried to run the nmake command from a command prompt at the top of the project .cpp file...
// Note: Proxy/Stub Information
// To build a separate proxy/stub DLL,
// run nmake -f SPDComps.mk in the project directory.

This is the error that I got.
fatal error C1189: You need a Windows2000 or later to run this stub because it uses the following features: NMAKE: error U1077: 'cl' return code '0x2'. Stop.

Lim Bio Liong wrote:
If you are using VC++ 6.0, you would need to build the proxy/stub project and dll manually.

I can also use SAFEARRAY's but I didn't have much better luck using them. I didn't seem to get anything back then. I may try that also. Maybe I have learned something more in the last few days of trying this... Smile | :)

David

Lim Bio Liong19-Aug-05 5:20