> Hi All,
>
[quoted text clipped - 29 lines]
> messages written by the dll to a file?? Is this a know issue? Has
> anyone faced this issue before?
This is a fundamental limitation - when you compile the DLL with VC6 and the
EXE with VC7{.1}, you have two different copies of the CRT each of which has
it's own table of "file handles". If you need to coordinate I/O between
modules compiled with different versions of the CRT (compiler), you'll need
to implement all of your I/O in terms of the base Win32 API (CreateFile,
WriteFile, etc).
The same situation will occur if you simply mix CRT versions with a single
compiler version (e.g. compile the DLL with /MD and compile the EXE with
/MT).
-cd
ndessai - 01 Jul 2004 04:30 GMT
Thanks for the mail.
Is there any work around by which I can meet my requirements.
The limitations on my side are the dll cannot be recompiled for the the
CRT since it is from third party. And I have moved my project to the new
compiler. Since the dll anyways prints all the messages to the console
screen, is there no way by which I can redirect it to a file without
changing the dll?
Please let me know.
Thanks,
Navanath
>>Hi All,
>>
[quoted text clipped - 42 lines]
>
> -cd
Carl Daniel [VC++ MVP] - 01 Jul 2004 06:42 GMT
> Thanks for the mail.
> Is there any work around by which I can meet my requirements.
[quoted text clipped - 6 lines]
> without
> changing the dll?
You might be able to use SetStdHandle to point STD_ERROR_HANDLE (and/or
STD_OUTPUT_HANDLE) to a file. I would think that that would catch I/O from
the DLL as well, but I don't have any way to test it in your environment.
If you try it, please post back with the results, good or bad.
-cd
ndessai - 02 Jul 2004 04:42 GMT
Hi Daniel,
Thanks for the suggestion. I had tried this earlier but to my dismay, it
did not work!!
Regards,
Navanath
>>Thanks for the mail.
>>Is there any work around by which I can meet my requirements.
[quoted text clipped - 14 lines]
>
> -cd
ndessai - 01 Jul 2004 04:30 GMT
Thanks for the mail.
Is there any work around by which I can meet my requirements.
The limitations on my side are the dll cannot be recompiled for the the
CRT since it is from third party. And I have moved my project to the new
compiler. Since the dll anyways prints all the messages to the console
screen, is there no way by which I can redirect it to a file without
changing the dll?
Please let me know.
Thanks,
Navanath
>>Hi All,
>>
[quoted text clipped - 42 lines]
>
> -cd
ndessai - 01 Jul 2004 04:34 GMT
Thanks for the mail.
Is there any work around by which I can meet my requirements.
The limitations on my side are the dll cannot be recompiled for the the
CRT since it is from third party. And I have moved my project to the new
compiler. Since the dll anyways prints all the messages to the console
screen, is there no way by which I can redirect it to a file without
changing the dll?
Please let me know.
Thanks,
Navanath
>>Hi All,
>>
[quoted text clipped - 42 lines]
>
> -cd
ndessai - 01 Jul 2004 04:44 GMT
Thanks for the mail.
Is there any work around by which I can meet my requirements.
The limitations on my side are the dll cannot be recompiled for the the
CRT since it is from third party. And I have moved my project to the new
compiler. Since the dll anyways prints all the messages to the console
screen, is there no way by which I can redirect it to a file without
changing the dll?
Please let me know.
Thanks,
Navanath
>>Hi All,
>>
[quoted text clipped - 42 lines]
>
> -cd