Jump to content

aqstws

Member
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About aqstws

  • Birthday 12/20/1954
  1. I have a rudimentary COM server working with a COM client. Both c++ objects were created on Visual Studio EXE2003. They work. I have a pool of 3 computers to show this. Now, I want to call the COM server on any of these 3 PC's from a different version of the COM client, written in c++ on a Linux workstation. I am fearful that the extra files made by Visual Studio which make the MIDL work in my purely Windows environment will be missing, or broken in ways that I will not be able to troubleshoot. I concede, there is a chance that all of the MIDL code resides in the server, and when I call
  2. I am using printf. I don't have a problem printing. Even cout prints. But my problem is not getting strings out. It's that I don't know why it breaks a COM function. I have other COM code problems, and so I am trying to make sure that every COM function I use works exactly how it should work. How can an unrelated c++ function have this effect on COM? I'm learnign COM. Its' COM that's showing me something I don't understand. Does COM set up a streaming path, like cout uses? The convenience of cout is that in the strongly typed code of c and c++, I don't need to know the variable ty
  3. I'm old at c++ but new to COM. coinitialize() works if I remove all uses of cout. If I include a single cout, such as cout << "top" << endl; anywhere in the code...even much later than my coinitialize call, coinitialize() fails. Of course I #include to get cout to compile. I am using Visual Studio 2003. A lot of trial and error has not worked for me yet. Has anyone had this observation and gotten around it? aqstws
×
×
  • Create New...