Search:

Type: Posts; User: cechen

Search: Search took 0.00 seconds.

  1. Hi Bubba, The parameter comes from unmanaged...

    Hi Bubba,

    The parameter comes from unmanaged c++ to managed memory, so garbage collector should not and would not touch it i guess...
  2. this was a quick response :) Hi again, in the...

    this was a quick response :)

    Hi again, in the both environment output directory is the same. So unmanaged dll and managed dll are written in the same directory.

    when i debug both DLLs in order...
  3. CornedBee, If you are there, strange things...

    CornedBee,

    If you are there, strange things happened to me.... for a couple of days the code ran fine, the values in the structs on both sides were the same after applying #pragma pack(1)...
  4. Yes this was the solution. #pragma pack(1)...

    Yes this was the solution. #pragma pack(1) directive made the size of the struct as it was in the unmanaged. Also adress of the pointer is true now... Thanks alot CornedBee!!! You saved me.

    i...
  5. you were right about the environment interpreting...

    you were right about the environment interpreting difference, the structure size is 265 bytes in vc++ 6.0 side (unmanaged), and 284 in vc++.net (managed) side. what can we do to avoid this problem...
  6. Yes you are right, GC cannot do anything with it...

    Yes you are right, GC cannot do anything with it cos this param has been created in the "caller" side. But i could not find any solution "why" the values became abnormal. (for ex. maxdeptvalue should...
  7. passing params between managed c++ and unmanaged c++

    Hi folks,

    I have a strange problem, seems to be Garbage Collector in managed memory. There is an unmanaged dll which makes a call to my managed dll with giving a structure as a parameter. Managed...
Results 1 to 7 of 7